From: Peter Kirk <peter.kirk@gmx.de>
To: Eric Wong <normalperson@yhbt.net>
Cc: git@vger.kernel.org
Subject: Re: git svn rebase creates some commits with empty author, commiter and date fields
Date: Wed, 26 Nov 2008 08:36:41 +0100 [thread overview]
Message-ID: <200811260836.48808.peter.kirk@gmx.de> (raw)
In-Reply-To: <20081125220617.GA21644@mayonaise>
On Tuesday 25 November 2008 23:06:17 Eric Wong wrote:
> 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?
This is the only svn server I use with git-svn with, so I don't know if this
would happen on other servers.
About "strange hooks"...there is a pre-commit hook verifying that the
svn:eolstyle is set properly on text files, but since git > 1.6.0 can do
"autoproperties" like svn that has never failed for me. Then there is a post-
commit hook which sends out a commit mail and scans the commit message for
certain commands which trigger the software to be built.
Since that other post I linked was related to the "authors" file, I added a
text file which maps all the svn users to git users, and that works (I can see
the assigned names instead of the svn names for commits that aren't broken),
but it hasn't helped reduce/eliminate the frequency of broken commits.
>
> Which version of the SVN perl bindings are you using?
I am using the SVN perl bindings that came with my distribution (ubuntu), the
version string reads: 1.5.1dfsg1-1ubuntu2, might this be the problem?
Peter
prev parent reply other threads:[~2008-11-26 7:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-18 10:21 git svn rebase creates some commits with empty author, commiter and date fields Peter Kirk
2008-11-25 22:06 ` Eric Wong
2008-11-26 7:36 ` Peter Kirk [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200811260836.48808.peter.kirk@gmx.de \
--to=peter.kirk@gmx.de \
--cc=git@vger.kernel.org \
--cc=normalperson@yhbt.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).