From: Madhu <enometh@meer.net>
To: git@vger.kernel.org
Subject: Re: git-cvsimport problem
Date: Wed, 28 May 2008 17:45:13 +0530 [thread overview]
Message-ID: <m3iqwytyjy.fsf@meer.net> (raw)
In-Reply-To: <482192B9.2010406@opensourceclub.org> (Alenoosh Baghumian's message of "Wed, 07 May 2008 16:00:01 +0430")
* Alenoosh Baghumian <482192B9.2010406@opensourceclub.org> :
Wrote on Wed, 07 May 2008 16:00:01 +0430:
| I run git-cvsimport in verbose mode and I see "* UNKNOWN LINE *
| Branches:" many times during execution , will that cause any problem ?
| And my repository doesn't include any branches ? so why do I see this
| message ?
You must be using the beta version of cvsps, cvsps-2.2b1
,---- From the CHANGELOG:
|
| 2.2b1
| - add a new line item in the PatchSet output which indicates which
| branches fork off from after this PatchSet. This is actually
| the only way to correctly indicate the branching. The 'Ancestor
| Branch' thing is actually broken by design, and is now deprecated.
`----
git-cvsimport uses the -A ancestor mechanism (after patching cvsps-2.1
for some corner cases), this ignores the Branches line.
I'd be interested in knowing the git-cvsimport authors' opinion on
reworking it to use the Branches mechanism.
--
Madhu
next prev parent reply other threads:[~2008-05-28 12:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-07 11:30 git-cvsimport problem Alenoosh Baghumian
2008-05-28 12:15 ` Madhu [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-04-30 5:55 Alenoosh Baghumian
2008-04-30 10:12 ` Michael Haggerty
2006-05-30 1:06 Grzegorz Kulewski
2006-05-30 1:56 ` Martin Langhoff
2006-05-30 4:37 ` Linus Torvalds
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=m3iqwytyjy.fsf@meer.net \
--to=enometh@meer.net \
--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).