git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Michael J Gruber <git@drmicha.warpmail.net>
To: Thomas Adam <thomas@xteddy.org>
Cc: git@vger.kernel.org, cvsps@dm.cobite.com
Subject: Re: git-cvsimport with cvsps output in commit msg breaks imports
Date: Fri, 10 Dec 2010 13:48:35 +0100	[thread overview]
Message-ID: <4D0221A3.6080706@drmicha.warpmail.net> (raw)
In-Reply-To: <20101209220347.GA3180@shuttle.home>

Thomas Adam venit, vidit, dixit 09.12.2010 23:03:
> Hi all,
> 
> [ I've Cced both the cvsps maintainer and the author listed for
> git-cvsimport in case it's more relevant to either tool. ]
> 
> I am wondering if anyone here is able to shed some light on a problem I've
> encountered with git-cvsimport.  For ages now, I've had an automatic
> conversion of a CVS repository to a Git one, using git-cvsimport to update a
> repository as commits happen in CVS.
> 
> The repository in question is here:
> 
> https://github.com/ThomasAdam/tmux
> 
> Everything is on the Master branch.
> 
> 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.
> 
> But I can't say for sure.

The previous one has cvsps info in the commit message already, prefixed
with "|". So the problem is the previous one or the one before.

If you have cvs checkout, can spot anything between those? Can you redo
the cvsps import from that point on and check cvsps log?

Michael

  reply	other threads:[~2010-12-10 12:56 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 [this message]
2010-12-10 19:58 ` Andreas Schwab

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D0221A3.6080706@drmicha.warpmail.net \
    --to=git@drmicha.warpmail.net \
    --cc=cvsps@dm.cobite.com \
    --cc=git@vger.kernel.org \
    --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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).