From: Yann Dirson <ydirson@altern.org>
To: Keith Packard <keithp@keithp.com>
Cc: Linus Torvalds <torvalds@osdl.org>,
Jim Meyering <jim@meyering.net>,
Git Mailing List <git@vger.kernel.org>,
Matthias Urlichs <smurf@smurf.noris.de>,
Pavel Roskin <proski@gnu.org>
Subject: Re: git-cvsimport doesn't quite work, wrt branches
Date: Thu, 15 Jun 2006 09:18:24 +0200 [thread overview]
Message-ID: <20060615071823.GE7766@nowhere.earth> (raw)
In-Reply-To: <1150224411.20536.79.camel@neko.keithp.com>
On Tue, Jun 13, 2006 at 11:46:51AM -0700, Keith Packard wrote:
> Yeah, we've got
>
> git-cvsimport
> cvsps
> cvs rlog
> ,v files
>
> cvs rlog is designed to 'represent' the history of the repository to
> users.
I wouldn't exactly call that "history of the repository" :)
Are you thinking about any particular information from the ,v files,
that rlog fails to expose ? That is, wouldn't be possible to do a job
similar to what parsecvs does, with remote support ?
Best regards,
--
Yann Dirson <ydirson@altern.org> |
Debian-related: <dirson@debian.org> | Support Debian GNU/Linux:
| Freedom, Power, Stability, Gratis
http://ydirson.free.fr/ | Check <http://www.debian.org/>
next prev parent reply other threads:[~2006-06-15 7:18 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
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 [this message]
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=20060615071823.GE7766@nowhere.earth \
--to=ydirson@altern.org \
--cc=git@vger.kernel.org \
--cc=jim@meyering.net \
--cc=keithp@keithp.com \
--cc=proski@gnu.org \
--cc=smurf@smurf.noris.de \
--cc=torvalds@osdl.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 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.