Messages in this thread | | | Subject | Re: bk commits and dates | From | Benjamin Herrenschmidt <> | Date | Thu, 10 Mar 2005 16:49:19 +1100 |
| |
On Wed, 2005-03-09 at 19:28 -0800, Linus Torvalds wrote: > > 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.
Yes, but it would be easy to have the messages dated from the day they are sent :) Even if you put the real commit date in the message itself. It's really disturbing to receive mails dated a long time in the past don't you think ?
> 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.
Yes, but the email gets the old date.
> 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..
Hah ok. Which James ?
Ben.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |