Re: git-svn blame change- doc confusion

From: Steven Grimm <koreth@midwinter.com>
Date: May 12, 2008, 06:33 UTC
Message-ID: <906678E9-D203-484B-8416-1C6079C74B2D@midwinter.com>
In-Reply-To: <449c10960805112105w2e362ea7l9b11c53c47952501@mail.gmail.com>

On May 11, 2008, at 9:05 PM, Dan McGee wrote:

> Here is the commit snippet. Reading the commit message, I would assume
> the default format with no options is SVN, and you need to use the
> --git-format arg to get the GIT format.

Yes, that's right. But note that "git format" does not mean "identical to the output of git blame" -- it means "lines are formatted the same way they are in git blame," meaning the revision ID (which in this case is an svn version number or 0 for any lines for which there isn't history in svn) then the committer name and commit timestamp enclosed in parentheses, then the line number with a trailing closing paren, then the contents of the line.

The svn format, by contrast, is the svn commit number, then the committer name, then the contents of the line.

> However, reading the --git-format description tells me something real
> weird- that using --git-format will give me SVN revision numbers and
> not git hashes, and something about revision 0?

Yes, that's also right. If you want git hashes, just run "git blame", which will work exactly the same as in a non-svn-linked git repository -- the whole point of having "git svn blame" is to view changes in terms of svn revisions rather than git hashes.

-Steve