From: Osamu Aoki <osamu.aoki@tc4.so-net.ne.jp>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>, git@vger.kernel.org
Subject: git <-> cvs synch script with git cvsexportcommit -W
Date: Wed, 12 Jul 2017 23:45:46 +0900 [thread overview]
Message-ID: <20170712144546.ac3pvwe3jwxqf675@tc4.so-net.ne.jp> (raw)
In-Reply-To: <alpine.DEB.2.21.1.1707121540460.4193@virtualbox>
Hi,
Here is my old mail with updated pointer. This may be useful for people
to migrate git to cvs while keeping cvs up-to-date.
On Wed, Jul 12, 2017 at 03:41:58PM +0200, Johannes Schindelin wrote:
> Hi,
>
> On Mon, 13 Jul 2015, Osamu Aoki wrote:
>
> > Thanks for "git cvsexportcommit -W" feature.
> > http://git.kernel.org/cgit/git/git.git/commit/?id=d775734c40afed216160437c59a45c93bdf28689
> >
> > It took me a while to get this working right. I may have made a bit of
> > error in the way, but it looks like I need to have
> >
> > $ cat .git/info/exclude
> > CVS
> >
> > to avaid error when commiting more than 2 commts. Is this what you
> > expect?
> >
> > I am trying to emulate git-svn for CVS using this and others. I am
> > making a first trial script as seen at:
> > https://wiki.debian.org/CvsusingGit
> > https://people.debian.org/~osamu/git-cvs.sh (my current trial script.)
Since then I updated wiki page and then moved script to github.
https://github.com/osamuaoki/git-cvs
> Sorry, this completely slipped through and bit-rotted in my inbox for two
> years (there are still 2,000+ friends in my inbox that paid your mail
> company).
Oh, well happens.
> Would you mind sending a mail about git-cvs.sh to git@vger.kernel.org for
> much wider visibility?
OK. Here we go.
Osamu
parent reply other threads:[~2017-07-12 16:01 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <alpine.DEB.2.21.1.1707121540460.4193@virtualbox>]
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=20170712144546.ac3pvwe3jwxqf675@tc4.so-net.ne.jp \
--to=osamu.aoki@tc4.so-net.ne.jp \
--cc=Johannes.Schindelin@gmx.de \
--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.
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).