From: Jonathan Nieder <jrnieder@gmail.com>
To: Guy Rouillier <guyr@burntmail.com>
Cc: git@vger.kernel.org, Emil Medve <Emilian.Medve@Freescale.com>,
Pascal Obry <pascal@obry.net>, Clemens Buchacher <drizzd@aon.at>,
Martin Langhoff <martin@laptop.org>
Subject: Re: cvsimport still not working with cvsnt
Date: Mon, 20 Dec 2010 15:36:54 -0600 [thread overview]
Message-ID: <20101220213654.GA24628@burratino> (raw)
In-Reply-To: <4D0ED5EC.9020402@burntmail.com>
(+cc: Emil, some cvsimport people)
Guy Rouillier wrote:
> I'm going to try sending this blind, as the mailing list has sent me
> the promised authorization key after 24 hrs.
No problem. Actually a subscription is not required --- the
convention on this list is to always reply-to-all.
> I finally found the problems, both of which were reported in 2008
> here:
>
> http://kerneltrap.org/mailarchive/git/2008/3/13/1157364
Seems to have received no replies[1].
> I do see one possible issue with the supplied modifications. At
> work, we upgraded from CVS to CVSNT. So, my home directory has both
> .cvspass (from the original CVS) and .cvs/cvspass (after the
> conversion to CVSNT.) Sloppy housekeeping on my part, I admit, but
> probably not uncommon. The supplied patch would pick up the
> original CVS file and would fail. (BTW, this is true only of the
> git-cvsimport.perl script itself; cvsps must shell out to the
> installed CVS client (in my case, cvsnt), because when I invoked
> that manually, it worked.)
>
> So, I would advise checking to see if both files exist, and if so
> exit with an error. Unless cvsimport wants to get real fancy and
> shell out to the installed cvs client to try to figure out what is
> installed, there is no way to tell which cvspass file is actively
> being used. I don't recommend trying to figure this out, as the
> user's intent is unclear.
Thanks, sounds sane to me. Care to write a patch?
Regards,
Jonathan
[1] http://thread.gmane.org/gmane.comp.version-control.git/77109
next prev parent reply other threads:[~2010-12-20 21:37 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-20 4:05 cvsimport still not working with cvsnt Guy Rouillier
2010-12-20 21:36 ` Jonathan Nieder [this message]
2010-12-21 22:09 ` Emil Medve
2010-12-22 5:43 ` Guy Rouillier
2011-01-10 7:33 ` Guy Rouillier
2011-01-10 15:38 ` Martin Langhoff
2011-01-14 6:38 ` Guy Rouillier
2011-01-14 7:44 ` Jonathan Nieder
2011-01-14 21:49 ` Junio C Hamano
2011-01-30 6:33 ` Guy Rouillier
2011-01-30 20:19 ` Martin Langhoff
2011-02-10 22:01 ` Junio C Hamano
2011-02-18 6:26 ` Guy Rouillier
2011-02-18 18:34 ` Junio C Hamano
2011-02-19 7:17 ` Guy Rouillier
2011-02-20 7:21 ` Junio C Hamano
2011-02-21 4:30 ` Guy Rouillier
2011-02-21 23:33 ` Junio C Hamano
2011-02-22 23:08 ` Junio C Hamano
2011-02-22 23:50 ` Martin Langhoff
2011-02-23 0:08 ` Guy Rouillier
2011-02-23 0:45 ` Junio C Hamano
2011-02-23 2:33 ` Guy Rouillier
2011-02-23 5:24 ` Junio C Hamano
2011-02-27 5:20 ` Guy Rouillier
2011-02-27 8:26 ` Junio C Hamano
2011-04-29 4:27 ` Guy Rouillier
2011-04-29 22:27 ` Jonathan Nieder
2011-05-01 5:33 ` Guy Rouillier
2011-05-01 18:44 ` Junio C Hamano
2011-02-23 0:42 ` Junio C Hamano
2011-02-24 3:14 ` Guy Rouillier
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=20101220213654.GA24628@burratino \
--to=jrnieder@gmail.com \
--cc=Emilian.Medve@Freescale.com \
--cc=drizzd@aon.at \
--cc=git@vger.kernel.org \
--cc=guyr@burntmail.com \
--cc=martin@laptop.org \
--cc=pascal@obry.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.