From: Christian Biesinger <cbiesinger@web.de>
To: unlisted-recipients:; (no To-header on input)
Subject: [PATCH] Ignore commits for which cvsps can't identify a branch
Date: Fri, 10 Feb 2006 22:02:33 +0100 [thread overview]
Message-ID: <200602102102.k1AL2Xkd010415@biesi.no-ip.org> (raw)
cvps sometimes can't identify a branch for a specific revision, it shows
messages like:
WARNING: revision 1.36.2.2 of file Makefile.in on unnamed branch
and uses #CVSPS_NO_BRANCH as branch name in its output.
This checkin makes it so that git-cvsimport ignores such branches, and when they
appear as ancestor branch, it maps them to HEAD.
Signed-off-by: Christian Biesinger <cbiesinger@web.de>
---
I tried to import the Mozilla CVS Repository into git, just for fun, and it
failed. This is one of the patches that are required for it.
I hope I did this right, I'm not so familiar with git...
Documentation/SubmittingPatches says to mail patches to the maintainer, who is
that? :)
git-cvsimport.perl | 11 +++++++++++
1 files changed, 11 insertions(+), 0 deletions(-)
ed142593c84ba76580e780ce8f12244214023213
diff --git a/git-cvsimport.perl b/git-cvsimport.perl
index 00fc3ba..4b8ca95 100755
--- a/git-cvsimport.perl
+++ b/git-cvsimport.perl
@@ -799,7 +799,18 @@ while(<CVS>) {
$state = 11;
next;
}
+ if ($branch eq "#CVSPS_NO_BRANCH") {
+ # skip
+ print "skip patchset $patchset: unknown branch\n" if $opt_v;
+ $state = 11;
+ next;
+ }
if($ancestor) {
+ if ($ancestor eq "#CVSPS_NO_BRANCH") {
+ # skip
+ print "In patchset $patchset: ancestor branch unknown, setting to $opt_o" if $opt_v;
+ $ancestor = $opt_o;
+ }
if(-f "$git_dir/refs/heads/$branch") {
print STDERR "Branch $branch already exists!\n";
$state=11;
--
1.1.6
next reply other threads:[~2006-02-10 21:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-10 21:02 Christian Biesinger [this message]
2006-02-10 21:21 ` [PATCH] Ignore commits for which cvsps can't identify a branch Junio C Hamano
2006-02-10 22:02 ` Christian Biesinger
2006-02-10 23:25 ` Linus Torvalds
2006-06-10 19:24 ` Yann Dirson
2006-06-10 19:45 ` Christian Biesinger
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=200602102102.k1AL2Xkd010415@biesi.no-ip.org \
--to=cbiesinger@web.de \
/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).