From: Michael Ellerman <michael@ellerman.id.au>
To: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: bk commits and dates
Date: Thu, 10 Mar 2005 14:44:01 +1100 [thread overview]
Message-ID: <200503101444.01651.michael@ellerman.id.au> (raw)
In-Reply-To: <1110422519.32556.159.camel@gaston>
[-- Attachment #1: Type: text/plain, Size: 1077 bytes --]
Two's company ...
On Thu, 10 Mar 2005 13:41, Benjamin Herrenschmidt wrote:
> While we are at such requests ...
>
> When you pull from one of the trees, like netdev, the commit messages
> are sent to the bk commit list with the original date stamp of the patch
> in the netdev tree.
>
> For example, if Jeff commited a patch from somebody in his netdev tree 3
> weeks ago, and you pull Jeff's tree today, we'll get all the commit
> messages today, but dated from 3 weeks ago.
>
> That means that in my mailing list archive, where my mailer sorts them
> by date, I can't say, for example, everything that is before the 2.6.11
> tag release was in 2.6.11. It's also difficult to spot "new" stuffs as
> they can arrive with dates weeks ago, and thus show up in places I will
> not look for.
>
> 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.
>
> Ben.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-03-10 3:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-10 2:41 bk commits and dates Benjamin Herrenschmidt
2005-03-10 3:28 ` Linus Torvalds
2005-03-10 5:49 ` Benjamin Herrenschmidt
2005-03-10 16:01 ` Linus Torvalds
2005-03-10 3:44 ` Michael Ellerman [this message]
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=200503101444.01651.michael@ellerman.id.au \
--to=michael@ellerman.id.au \
--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