From: Andreas Schwab <schwab@linux-m68k.org>
To: Thomas Adam <thomas@xteddy.org>
Cc: git@vger.kernel.org, cvsps@dm.cobite.com, smurf@smurf.noris.de
Subject: Re: git-cvsimport with cvsps output in commit msg breaks imports
Date: Fri, 10 Dec 2010 20:58:27 +0100 [thread overview]
Message-ID: <m2ei9p8knw.fsf@igel.home> (raw)
In-Reply-To: <20101209220347.GA3180@shuttle.home> (Thomas Adam's message of "Thu, 9 Dec 2010 22:03:49 +0000")
Thomas Adam <thomas@xteddy.org> writes:
> More specifically, the commit which I think introduced the problem, and all
> subsequent commits thereafter is here:
>
> https://github.com/ThomasAdam/tmux/commit/f0220a10b01a764e0dc52ea1b2407f58600a30eb
>
> Note that from this commit onwards, the commit *message* has a bunch of
> cvsps output in it. I can only surmise that this somehow causes problems
> for cvsimport.
The cvsps output is ambigous. If the commit log includes text that
resembles the patchset format generated by cvsps then git-cvsimport can
easily get confused.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
prev parent reply other threads:[~2010-12-10 19:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-09 22:03 git-cvsimport with cvsps output in commit msg breaks imports Thomas Adam
2010-12-10 12:48 ` Michael J Gruber
2010-12-10 19:58 ` Andreas Schwab [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=m2ei9p8knw.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=cvsps@dm.cobite.com \
--cc=git@vger.kernel.org \
--cc=smurf@smurf.noris.de \
--cc=thomas@xteddy.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).