On 05/29/13 05:24, Jordan Justen wrote:
> Well, svn loses the true author of the commit
Actually, we're more lucky than that, I just found out recently (yes,
yes, I should have read the entire git-svn manual as first step):
If you pass "--use-log-author" to the initial "git svn clone", and also
to all subsequent "git svn rebase" commands -- actually, to anything
that does "git svn fetch" internally), then git-svn picks the first
S-o-b (or From:) line from the commit message and uses that as author
string ("git commit --author=...").
I've been using this for a while now and it works great, especially
because */Contributions.txt mandates, under Code Contributions / 2.,
that any commit message include S-o-b.
You might even consider rebuilding the unofficial git mirrors on
github/SF from scratch -- some users would have to rebase a few
branches, but hey them git mirrors have always been unofficial :)
Anyhow if at one point the project decides to move to git officially,
--use-log-author would probably be a good idea.
Laszlo
------------------------------------------------------------------------------
Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
Get 100% visibility into your production application - at no cost.
Code-level diagnostics for performance bottlenecks with <2% overhead
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap1
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/edk2-devel
