This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: onwards to git

From: Andreas Schwab <schwab at linux-m68k dot org>
To: Jim Meyering <jim at meyering dot net>
Cc: libc-alpha at sources dot redhat dot com, Paolo Bonzini <bonzini at gnu dot org>
Date: Wed, 06 May 2009 00:44:29 +0200
Subject: Re: onwards to git
References: <49F89C2D.5060702@redhat.com><20090501194544.GP21271@machine.or.cz> <49FEC77B.6050307@gnu.org><87ocu8zql6.fsf@meyering.net> <874ovzw929.fsf@meyering.net>

Jim Meyering <jim@meyering.net> writes:

> One is very much like the existing glibc.git, with over 64k commits on
> the trunk/master.  The other has the same content, but with aggregated
> change sets (and usually-better commit log messages[*]), so there are
> only 13k commits.

It appears the process of aggregation has clobbered the committer in
some commits.  For example 03f1681f in glibc1.git has Ulrich as the
committer with the same timestamp as the committer of the original child
031fc0c9 in glibc2.git.

I would also suggest to filter out all commits with the "file ... was
initially add on branch ..." commit message.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Follow-Ups:
- Re: onwards to git
  - From: Jim Meyering

References:
- Re: onwards to git
  - From: Petr Baudis
- Re: onwards to git
  - From: Paolo Bonzini
- Re: onwards to git
  - From: Jim Meyering
- Re: onwards to git
  - From: Jim Meyering

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]