Git development
 help / color / mirror / Atom feed
From: Francis Galiegue <fg@one2team.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] git-cvsimport.perl: use human readable names for option values
Date: Mon, 3 Nov 2008 11:32:20 +0100	[thread overview]
Message-ID: <200811031132.20590.fg@one2team.com> (raw)
In-Reply-To: <200811031031.59196.fg@one2team.net>

Le Monday 03 November 2008 10:31:59 Francis Galiegue, vous avez écrit :
> Hello,
>
> As I am keen to make my company use git eventually, but they have a really,
> really messy CVS tree that git-cvs*.perl cannot handle right now, I've
> decided to have a serious look at the code.
>

As stated in one mail I sent earlier on, the real problem is that 
git-cvsimport won't detect empty branches for two reasons:

* it relies on cvsps output, which doesn't tell about it either;
* however, it doesn't make use of another file that cvsps generates in 
$HOME/.cvsps by default, which can help about giving this information.

I'll try the following:

* instead of capturing cvsps output directly, I'll use its -p option, which 
has the advantage of generating one file per patchset;
* I'll consolidate the information of the other generated file in a hash and 
correlate the information found in there with the individual patchset: my 
hope is that I'll be able to detect so-far undetected branches and create 
them.

-- 
Francis Galiegue
ONE2TEAM
Ingénieur système
Mob : +33 (0) 6 83 87 78 75
Tel : +33 (0) 1 78 94 55 52
fge@one2team.com
40 avenue Raymond Poincaré
75116 Paris

      reply	other threads:[~2008-11-03 10:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-03  9:31 [PATCH] git-cvsimport.perl: use human readable names for option values Francis Galiegue
2008-11-03 10:32 ` Francis Galiegue [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=200811031132.20590.fg@one2team.com \
    --to=fg@one2team.com \
    --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