[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080213001650.GY18625@fieldses.org>
Date: Tue, 12 Feb 2008 19:16:50 -0500
From: "J. Bruce Fields" <bfields@...ldses.org>
To: Al Viro <viro@...IV.linux.org.uk>
Cc: David Miller <davem@...emloft.net>, jeff@...zik.org,
linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
torvalds@...ux-foundation.org, linville@...driver.com
Subject: Re: Announce: Linux-next (Or Andrew's dream :-))
On Tue, Feb 12, 2008 at 11:54:01PM +0000, Al Viro wrote:
> On Tue, Feb 12, 2008 at 03:51:07PM -0800, David Miller wrote:
> > From: Jeff Garzik <jeff@...zik.org>
> > Date: Tue, 12 Feb 2008 11:31:48 -0500
> >
> > > I understand the desire to want a nice and clean history, but the
> > > frequency here really has a negative impact on your downstreams.
> >
> > Ok, fair enough. Any alternative suggestions on how to remove turds
> > without them being in the history?
> >
> > > It also totally screws the commit statistics, wiping me and John and the
> > > committers we have preserved out, replacing everybody's committer with
> > > David Miller.
> >
> > I am well aware of this downside, sorry.
>
> Ahem... Use of git-cherry-pick preserves commit information just fine.
Not by default, at least (note they said "commiters", not "authors"):
bfields@pig:~/local/linux-2.6$ git cherry-pick v2.6.25-rc1
Finished one cherry-pick.
Created commit c445dc0: Linux 2.6.25-rc1
1 files changed, 2 insertions(+), 2 deletions(-)
bfields@pig:~/local/linux-2.6$ git show --pretty=raw HEAD
commit c445dc0a8b11877d6038dc528254733348c9f110
tree 4018d5d93f857d946dd89acbb4e45c9da04eadaf
parent b6ce068a1285a24185b01be8a49021827516b3e1
author Linus Torvalds <torvalds@...dy.linux-foundation.org> 1202681894 -0800
committer J. Bruce Fields <bfields@...i.umich.edu> 1202861481 -0500
--b.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists