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

Re: git-svn bug?

From
Shawn Pearce <spearce@spearce.org>
Date
Nov 15, 2006, 22:37 UTC
Message-ID
<20061115223709.GG24861@spearce.org>
In-Reply-To
<m2psbocpbo.fsf@ziti.local>
Seth Falcon <sethfalcon@gmail.com> wrote:
Show 5 quoted lines
> I always send commits as:
> 
> git-svn dcommit remotes/git-svn..master
> 
> Possibly replacing master with whatever git branch I'm working on.
Or just:
   git-svn dcommit remotes/git-svn..
to send the current branch.
> One nice thing about this approach is that you can sort of preview the
> commit as:
> 
>   git diff remotes/git-svn..master
Or see the log and patch of each commit on the current branch:
   git log -p remotes/git-svn..
Previous: Seth FalconNext: Seth Falcon
Message 8 of 10 in “git-svn bug?”
  1. Troy TelfordNov 15, 2006
  2. Junio C HamanoNov 15, 2006
  3. Troy TelfordNov 15, 2006
  4. Eric WongNov 17, 2006
  5. Troy TelfordNov 17, 2006
  6. Eric WongNov 19, 2006
  7. Seth FalconNov 15, 2006
  8. Shawn PearceNov 15, 2006
  9. Seth FalconNov 16, 2006
  10. Troy TelfordNov 15, 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.