From: Linus Torvalds <torvalds@osdl.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: bk commits and dates
Date: Wed, 9 Mar 2005 19:28:00 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.58.0503091924170.2530@ppc970.osdl.org> (raw)
In-Reply-To: <1110422519.32556.159.camel@gaston>
On Thu, 10 Mar 2005, Benjamin Herrenschmidt wrote:
>
> I don't know if I'm the only one to have a problem with that, but it
> would be nice if it was possible, when you pull a bk tree, to have the
> commit messages for the csets in that tree be dated from the day you
> pulled, and not the day when they went in the source tree.
Nope, that's against how BK works. It's really distributed, so "my" tree
has no special meaning, and as such the fact that I pull has no meaning
either - it doesn't trigger as anything special.
The only thing that ends up being special is when it hits the public tree
which has the trigger to send out the emails. IOW, the date of the _email_
is special (in that it says when a commit hit the public tree), not not
the commits changesets themselves.
Now, if James trigger scripts set the date of the email by the date of the
commit, that sounds like a misfeature, but you'd better talk to James, not
me, since he's the one doing that part..
Linus
next prev parent reply other threads:[~2005-03-10 3:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-10 2:41 Benjamin Herrenschmidt
2005-03-10 3:28 ` Linus Torvalds [this message]
2005-03-10 5:49 ` Benjamin Herrenschmidt
2005-03-10 16:01 ` Linus Torvalds
2005-03-10 3:44 ` Michael Ellerman
2005-03-10 3:47 ` David S. Miller
2005-03-10 5:50 ` Benjamin Herrenschmidt
2005-03-10 6:13 ` Jeff Garzik
2005-03-10 14:11 ` David Woodhouse
2005-03-10 18:18 ` Tom Rini
2005-03-10 19:12 ` Olaf Hering
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.58.0503091924170.2530@ppc970.osdl.org \
--to=torvalds@osdl.org \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®