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
Feb 16, 2006, 06:57 UTC
Message-ID
<7vk6bvhju6.fsf@assigned-by-dhcp.cox.net>
* Master branch has these since 1.2.1 maintenance release.
  - documentation fixes:
    git-commit: Now --only semantics is the default.
  - usability:
    - rebase aquired a hook to refuse rebasing.
    - commit and add detects misspelled pathspec while making a partial commit.
    - git-svnimport: -r adds svn revision number to commit messages
    - properly git-bisect reset after bisecting from non-master head
    - send-email: Add some options for controlling how addresses
      are automatically added to the cc: list.
    - send-email: Add --cc
* Next branch has these, that are not in master.  If you feel
  you would benefit from these, testing and feedback is greatly
  appreciated.
 - "Assume unchanged git" series (7 commits):
   This was done in response to people on filesystems with slow
   lstat(2).  I do not have such an environment, so I cannot say
   I tested it that much.
 - "Rebase to different branch" (1 commit):
   This was previously discussed on the list.  With this command
   line:
    	$ git rebase --onto master~1 master topic
    
   would rebase this ancestry graph to:
    
              A---B---C topic
             /
        D---E---F---G master
    
    
   another graph that looks like this:
    
                  A'--B'--C' topic
                 /
        D---E---F---G master
   Earlier, you couldn't rebase to anywhere other than on top of
   "the other branch".
* Proposed updates "pu" branch has these, not in "next".  Some
  of them are of iffy nature, and without further work will not
  go anywhere.
 - "merge-tree" series by Linus (2 commits).
   I haven't spent enough time looking at and thinking about
   this yet.
 - "reuse pack data" (1 commit).
   I still haven't seen data corruption with this one, which is
   a good sign, but would like to keep beating it privately for
   a while.  Perhaps will graduate to "next" by next week.
 - "bind commit" series (6 commits).
   I think the core-side is more or less done with this one.
   Anybody interested in doing Porcelain side?
 - "shallow clone" series (1 commit).
   I should drop this one for now and perhaps when enough people
   are interested reopen the issue.
Message 1 of 1 in “What's in git.git”
  1. Junio C HamanoFeb 16, 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.