Re: What's in git.git

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Nov 19, 2006, 15:17 UTC
Message-ID: <Pine.LNX.4.63.0611191547460.13772@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To: <7v1wo0bb4z.fsf@assigned-by-dhcp.cox.net>

Hi,

On Sat, 18 Nov 2006, Junio C Hamano wrote:

Show 12 quoted lines

> Junio C Hamano <junkio@cox.net> writes:
> 
> >  - 'pu' has the shallow clone WIP and a half-finished rewrite of
> >    git branch in C, both by Johannes.  Both needs a bit more
> >    polishing and confidence building before going into 'next',
> >    and given the recent discussion of enhancing branch
> >    management for pulls/pushes, it might be easier to drop the
> >    latter for now.
> 
> OOPS; sorry but the latter half is entirely untrue.  What's
> there is half-done git-shortlog.  Scratch everything about
> branch management please.

IMHO -shortlog needs support to read .mailmap, and maybe nods to throw out the built-in mailmap which is totally specific to the Linux kernel development.

As for shallow clone support: I am a bit underwhelmed by the enthusiasm to test this thing by the people I thought would be most interested. It really could be the case that it is not needed at all.

Just for the record, though: AFAICT the shallow stuff is lacking support for at least pushing from/into shallow repos and it should avoid making a commit shallow unnecessarily. And quite likely there are a few thinkos in it, so it would not hurt having more test cases (notably of things I did not think of), and some bad-ass testing with huge amounts of commits and files which were added/modified identically in different commits.

Ciao, Dscho