From: Keith Packard <keithp@keithp.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: keithp@keithp.com, Jim Meyering <jim@meyering.net>,
Git Mailing List <git@vger.kernel.org>,
Matthias Urlichs <smurf@smurf.noris.de>,
Yann Dirson <ydirson@altern.org>, Pavel Roskin <proski@gnu.org>
Subject: Re: git-cvsimport doesn't quite work, wrt branches
Date: Tue, 13 Jun 2006 11:46:51 -0700 [thread overview]
Message-ID: <1150224411.20536.79.camel@neko.keithp.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0606131008470.5498@g5.osdl.org>
[-- Attachment #1: Type: text/plain, Size: 542 bytes --]
On Tue, 2006-06-13 at 10:20 -0700, Linus Torvalds wrote:
> Well, it's a cvsps problem.
>
> Big surprise.
Yeah, we've got
git-cvsimport
cvsps
cvs rlog
,v files
cvs rlog is designed to 'represent' the history of the repository to
users. Cvsps was built as a software analysis tool, and is used by
putative software engineering researchers. Basing a supposedly lossless
repository conversion system on this pair seems foolish to me,
notwithstanding the heroic efforts to make it work.
--
keith.packard@intel.com
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-06-13 18:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-13 16:41 git-cvsimport doesn't quite work, wrt branches Jim Meyering
2006-06-13 17:06 ` Jakub Narebski
2006-06-13 17:20 ` Linus Torvalds
2006-06-13 18:46 ` Keith Packard [this message]
2006-06-13 22:55 ` Martin Langhoff
2006-06-13 23:30 ` Keith Packard
2006-06-14 1:56 ` Martin Langhoff
2006-06-14 9:37 ` sf
2006-06-15 7:18 ` Yann Dirson
2006-06-13 21:13 ` Yann Dirson
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=1150224411.20536.79.camel@neko.keithp.com \
--to=keithp@keithp.com \
--cc=git@vger.kernel.org \
--cc=jim@meyering.net \
--cc=proski@gnu.org \
--cc=smurf@smurf.noris.de \
--cc=torvalds@osdl.org \
--cc=ydirson@altern.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;
as well as URLs for NNTP newsgroup(s).