git/list[1] front-page[2] threads[3] people[4] search[5] about
 

What's in git.git

From
Junio C Hamano <junkio@cox.net>
Date
Jan 25, 2006, 13:00 UTC
Message-ID
<7vy814qx6o.fsf@assigned-by-dhcp.cox.net>
I've pushed out the following changes to "master" branch:
 * git-clone
   . --naked option is still accepted but is deprecated.  Please
     say --bare.
   . a repository cloned with --bare does not get "origin"
     branch, nor remotes/origin file.
   . Earlier we accepted more than one -o options, without
     complaining.  We now complain.
 * fetch and peek/ls-remote (Michal Ostrowski)
   . --upload-pack option to the underlying git-peek-remote and
     friends can be passed from the barebone Porcelain.
 * local push/pull environment fix (Matt Draisey)
   . We now clean "GIT_DIR" and friends from the environment
     when spawning a program on the other end to drive git
     native protocols on a local machine.  This uses unsetenv(),
     which is not strictly portable, but I was too lazy to fix
     it myself.  I am hoping that Jason Riedy will scream and
     give us a patch to make it work again on his Solaris box
     ;-).
 * sample update-hook rewrite (Andreas Ericsson)
 * asciidoc --unsafe workaround (Pavel Roskin)

In the "pu" branch, there are some interesting changes. The most immediately visible usability enhancement is the "combined diff" option to git-diff-tree command. Interested people can try something like this:

	$ git checkout pu
	$ make clean strip all install
	$ git checkout master

Do not forget to come back to your "master" branch once you are done, or your next pull would be screwed.

        $ git whatchanged --cc --abbrev pu

This would show an improved version of "git whatchanged -m -p". The difference is that it uses the "dense combined diff" suggested by Linus yesterday. Commits near the tip of "pu" tend to be Octopus, and you would see quite interesting combined diffs for them. I am not proud of the implementation itself, and I am sure there are more bugs to be discovered, but overall I am reasonably happy with what it shows. Once it stabilizes, it would be a good addition to gitweb UI. In addition to the "commitdiff" next to each parent, there would be an extra link in a merge commit to get a combined diff.

The "annotate helper" change by Linus and "bound commit" subproject support experiments are there as before.

There are other minor fixes and enhancements. Not all of them may make it to "master":

 * "diff-tree --abbrev --pretty" was still showing full 40
   characters of commit object names on "Merge:" line.
 * "rev-parse --abbrev[=<n>] $rev" is similar to
   "rev-parse --verify $rev", except that it shows an
   abbreviated object name.
 * The flag argument was handled confusingly by "rev-parse
   [--flags|--no-flags]".  The command now treats anything that
   come after --flags/--no-flags things to be parsed, not an
   option to control what the command does.  This was primarily
   needed to allow parsing out "--abbrev" option and giving it
   to "diff-tree" inside whatchanged.  All existing users have
   been adjusted to this change.  I do not think any of Cogito,
   gitk, nor stgit is affected.
Next: Jason Riedy
Message 1 of 6 in “What's in git.git”
  1. Junio C HamanoJan 25, 2006
  2. Jason RiedyJan 25, 2006
  3. Junio C HamanoJan 25, 2006
  4. Junio C HamanoJan 25, 2006
  5. Junio C HamanoJan 26, 2006
  6. Santi BejarJan 26, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.