From: Thomas Guyot-Sionnest <dermoth@aei.ca>
To: git@vger.kernel.org
Subject: [PATCH] git-svn bug with blank commits and author file
Date: Tue, 22 Apr 2008 06:07:47 -0400 [thread overview]
Message-ID: <480DB8F3.5080000@aei.ca> (raw)
[-- Attachment #1: Type: text/plain, Size: 926 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
* Sorry for resending; added a patch tag and corrected typo in subject *
When trying to import from svn using an author file, git-svn bails out
if it encounters a blank author. The attached patch changes this
behavior and allow using the author file with blanks authors.
I came across this bug while importing from a cvs2svn repo where the
initial revision (1) has a blank author. This doesn't break the behavior
of bailing out when an unknown author is encountered.
The patch was made against Git's HEAD.
If you reply please make sure to cc me as I'm not subscribed to the list.
Thanks,
- --
Thomas Guyot
dermoth@aei.ca
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFIDbjz6dZ+Kt5BchYRAjdFAJ0WA9TiIJ6tefjaPkd40Y2Tjv6NPACbBwmB
a6eFU84MpJ9MW1nErxDiqHY=
=k3jA
-----END PGP SIGNATURE-----
[-- Attachment #2: git-svn.perl-no_author.patch --]
[-- Type: text/plain, Size: 436 bytes --]
--- git-svn.perl.orig 2008-04-19 05:58:10.000000000 -0400
+++ git-svn.perl 2008-04-19 19:50:40.000000000 -0400
@@ -2375,8 +2375,7 @@
my ($author) = @_;
if (!defined $author || length $author == 0) {
$author = '(no author)';
- }
- if (defined $::_authors && ! defined $::users{$author}) {
+ } elsif (defined $::_authors && ! defined $::users{$author}) {
die "Author: $author not defined in $::_authors file\n";
}
$author;
next reply other threads:[~2008-04-22 10:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-22 10:07 Thomas Guyot-Sionnest [this message]
2008-04-22 23:23 ` [PATCH] git-svn bug with blank commits and author file Eric Wong
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=480DB8F3.5080000@aei.ca \
--to=dermoth@aei.ca \
--cc=git@vger.kernel.org \
/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).