threads / discuss / 3730

What's in git.git

Subject: What's in git.git

## tl;dr

One message between Mar 26, 2006 and Mar 26, 2006.

replies: 0people: 1as markdown or json

Junio C Hamano· Mar 26, 2006, 06:00 UTC · lore
* The 'master' branch has these since the last announcement.
 - git-svn memory usage reduction (Eric Wong)
 - documentation updates (Francis Daly, Jon Loeliger)
 - fix updating working tree after cvsimport reads from CVS
 - fetch exits non-zero when fast-forward check fails.
 - improve git-pull's failur case when pulling into the tracking branch.
 - commit-tree checks return value from write_sha1_file().
 - git-apply understands "@@ -l, +m @@" correctly.
----------------------------------------------------------------
* The 'next' branch, in addition, has these.

These are harmless and useful to be pushed into "master"; I just have not gotten around to.

 - updates around git-clone:
   . --use-separate-remote
   . --reference <repo>
   . fetch,parse-remote,fmt-merge-msg: refs/remotes/* support (Eric Wong)
   . sha1_name() understands refs/remotes/$foo/HEAD
 - sha1_name safety and core.warnambiguousrefs
 - git-merge knows some strategies want to skip trivial merges
------------

I really should do some more stats on this and push it out. Just haven't got around to do so.

 - insanely fast rename detection (Linus and me)
------------

These look very good, but people depend on them, so I'd like to simmer them in "next" for a couple of days to hear success stories, or "ah crap I got burned" story ;-).

 - tar-tree updates (Rene Scharfe)
 - send-email updates (Eric Wong)
------------
Hot off the press.  I smell the beginning of a good stuff here.
 - truly built-in diff (Linus with Davide)
------------

This is harmless to be pushed into "master" but is staying here only because nobody expressed urgency.

 - ls-{files,tree} --abbrev (Eric Wong)
----------------------------------------------------------------
* The 'pu' branch, in addition, has these.

Since I do not have a good guinea pig case to use this, I haven't read and understood the code being patched enough to comment on the change this one introduces; it looks obviously correct, though.

I'd like an ACK or two from people who works with SVN gateway before I apply this to "master".

 - git-svnimport: if a limit is specified, respect it (Anand Kumria)
------------

This script does what it claims to do, but I do not think of a useful use case for this. When I have packs with garbage objects in them (because I rewind my "pu" branch I usually end up having a handful in my packs), I just run "repack -a -d" and that is good enough. So I need a bit of convincing to keep this.

 - Add git-explode-packs (Martin Atukunda)

← back to recent threads