From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "David S. Miller" <davem@davemloft.net>
Cc: Linus Torvalds <torvalds@osdl.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: bk commits and dates
Date: Thu, 10 Mar 2005 16:50:21 +1100 [thread overview]
Message-ID: <1110433821.32524.176.camel@gaston> (raw)
In-Reply-To: <20050309194744.6aef66b7.davem@davemloft.net>
On Wed, 2005-03-09 at 19:47 -0800, David S. Miller wrote:
> On Thu, 10 Mar 2005 13:41:59 +1100
> Benjamin Herrenschmidt <benh@kernel.crashing.org> 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.
>
> When I'm working, I just do "bk csets" after I pull from Linus's
> tree to review what went in since the last time I pulled.
Yes, but the commit list archive is handy. I have quite good search
capabilities in my mailer for example, and sometimes, when doign
regression, it's quite useful to browse what went in between two
releases with it (it's just more handy than bk csets).
Ben.
next prev parent reply other threads:[~2005-03-10 5:57 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
2005-03-10 3:47 ` David S. Miller
2005-03-10 5:50 ` Benjamin Herrenschmidt [this message]
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=1110433821.32524.176.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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