From: Guy Rouillier <guyr@burntmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Martin Langhoff <martin@laptop.org>,
Jonathan Nieder <jrnieder@gmail.com>,
Emil Medve <Emilian.Medve@freescale.com>,
git <git@vger.kernel.org>, Pascal Obry <pascal@obry.net>,
Clemens Buchacher <drizzd@aon.at>
Subject: Re: cvsimport still not working with cvsnt
Date: Wed, 23 Feb 2011 22:14:26 -0500 [thread overview]
Message-ID: <4D65CD12.3070903@burntmail.com> (raw)
In-Reply-To: <7vei6zbmz8.fsf@alter.siamese.dyndns.org>
On 2/22/2011 7:42 PM, Junio C Hamano wrote:
> Martin Langhoff<martin@laptop.org> writes:
>
>> On Tue, Feb 22, 2011 at 6:08 PM, Junio C Hamano<gitster@pobox.com> wrote:
>>> Even though I don't deeply care about what CVSNT does...
>> ...
>>> Does anybody know why? Only to make things incompatible, perhaps? ;-)
>>
>> A brief googling around shows that it also stores it in the Windows registry.
>
> Yes, I saw that too. I actually also got the impression that registry is
> the primary location for cvsnt (hence I suspect .cvs/cvspass support might
> be secondary and would not be surprised if it were sub-par).
There may perhaps be a misunderstanding of CVSNT. CVSNT is a
multi-platform client and server. Both parts can run on many platforms,
including Windows, Linux, and Solaris. I don't use Macs so don't know
about them.
Use of HOME/.cvs/cvspass is not secondary or sub-par. On any platform
other than Windows, HOME/.cvs/cvspass is the standard place that CVSNT
stores repository passwords. And on Windows, you can optionally tell it
to store repository passwords in HOME/.cvs/cvspass instead of the
registry. I have my Windows configured that way for consistency with my
numerous Linux accounts.
The whole reason I resurrected this 2 year old topic is that we are
trying to migrate from CVSNT on *Linux* to git.
Thanks.
--
Guy Rouillier
prev parent reply other threads:[~2011-02-24 3:15 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
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 [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=4D65CD12.3070903@burntmail.com \
--to=guyr@burntmail.com \
--cc=Emilian.Medve@freescale.com \
--cc=drizzd@aon.at \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.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.