Re: git svn rebase creates some commits with empty author, commiter and date fields

[Eric Wong <normalperson@yhbt.net>]

Peter Kirk <peter.kirk@gmx.de> wrote:
> Hi there,
> 
> I am using git version 1.6.0.3, which I compiled myself from sources on my 
> linux/amd64 box which runns kubuntu 8.10.
> 
> Now, when I do "git svn clone" to retrieve the entire history from the svn 
> server then everything works fine. Then I start working with this, commit some 
> myself, and run "git svn rebase" frequently. What happens (and I don't see the 
> pattern) is that *some* commits that are retrieved via "git svn rebase" are 
> broken...they don't contain a valid author field, the date is at 1970 and, most 
> importantly (for me) the commit message is empty except for the "git-svn-id:" 
> line that "git svn" adds automatically. The diff is fine, and I can still use 
> the checkout fine...but I cannot view the log-message/author/date of some 
> commits, which becomes tiresome quickly.
> The only way to "fix" these broken commits is to do a clean "git svn clone", 
> but as new commits are pulled via "git svn rebase", my repository will again 
> become polluted with broken commits.

Weird.

Does this happen on other repositories you may use as well?  Do you know
of any strange hooks or otherwise non-standard setup with the SVN
server?

Which version of the SVN perl bindings are you using?

-- 
Eric Wong