From: Martin Langhoff <martin.langhoff@gmail.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: git@vger.kernel.org
Subject: Re: Pointers to CVS 2 GIT imports and gateways
Date: Mon, 9 May 2005 17:41:13 +1200 [thread overview]
Message-ID: <46a038f905050822413ece89b9@mail.gmail.com> (raw)
In-Reply-To: <427EEB9E.9070701@zytor.com>
On 5/9/05, H. Peter Anvin <hpa@zytor.com> wrote:
> What would be the point? The reason for bkcvs was that bk wasn't
> available to everyone.
Ease of transition for other automated tasks, perhaps? I don't know
what bits and pieces of infrastructure hang from the old BK-CVS
changeset distribution infrastructure.
Some projects do count on CVS gateways even if they use smarter SCMs.
This is not just because of licensing issues -- sometimes portability
and preexisting tools trump SCM changes.
regards,
martin
next prev parent reply other threads:[~2005-05-09 5:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-08 23:16 Pointers to CVS 2 GIT imports and gateways Martin Langhoff
2005-05-09 4:48 ` H. Peter Anvin
2005-05-09 5:41 ` Martin Langhoff [this message]
2005-05-09 13:30 ` H. Peter Anvin
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=46a038f905050822413ece89b9@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=git@vger.kernel.org \
--cc=hpa@zytor.com \
/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).