From: Junio C Hamano <gitster@pobox.com>
To: Sean <seanlkml@sympatico.ca>
Cc: Michael Haggerty <mhagger@alum.mit.edu>,
"Shawn O. Pearce" <spearce@spearce.org>,
git@vger.kernel.org
Subject: Re: Questions about git-fast-import for cvs2svn
Date: Sun, 15 Jul 2007 11:55:59 -0700 [thread overview]
Message-ID: <7vd4ytebsw.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20070715120149.3271b736.seanlkml@sympatico.ca> (seanlkml@sympatico.ca's message of "Sun, 15 Jul 2007 12:01:49 -0400")
Sean <seanlkml@sympatico.ca> writes:
> Will take a stab at answering your questions...
>
>> 1. Is it a problem to create blobs that are never referenced? The
>> easiest point to create blobs is when the RCS files are originally
>> parsed, but later we discard some CVS revisions, meaning that the
>> corresponding blobs would never be needed. Would this be a problem?
>
> Not a problem. Running "git gc" later will cleanup any unused objects.
>
>> 2. It appears that author/committer require an email address. How
>> important is a valid email address here?
>
> It's not necessary for the operation of Git itself; it's up to you to
> decide how important the information is to your project. You should
> be able to set an empty email address for author or committer in
> git fast-import as "name <>".
Don't do this; git-cvsimport and git-svn uses "name <name>"
which is a saner compromise. This way, you can add .mailmap to
help later "git shortlog" to map using "<name>" part to more
human friendly name. Mapping at conversion time would also be
good and git-cvsimport knows about it (I do not know about
git-svn).
>> b. CVS tag/branch creation events do not even include a username.
>> Any suggestions for what to use here?
>
> Perhaps just use your own username or one specifically created to
> run the conversion process.
I'd suggest to take the person and time information from the
commit that is tagged; that way you can keep the conversion
stable (iow, two conversoin runs using the same input data would
produce identical result).
In git we do not record "branch creation event". Also you can
use lightweight tags which does not have its own data -- which
means you do not have to come up with "the person who made the
tag".
>> 3. I expect we should set 'committer' to the value determined from CVS
>> and leave 'author' unused. But I suppose another possibility would be
>> to set the 'committer' to 'cvs2svn' and the 'author' to the original CVS
>> author. Which one makes sense?
I would set both to "name <name>" from CVS information.
next prev parent reply other threads:[~2007-07-15 18:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-15 14:11 Questions about git-fast-import for cvs2svn Michael Haggerty
2007-07-15 16:01 ` Sean
2007-07-15 18:51 ` Steffen Prohaska
2007-07-15 18:58 ` Steffen Prohaska
2007-07-15 18:55 ` Junio C Hamano [this message]
2007-07-16 3:35 ` Eric Wong
2007-07-15 18:43 ` Linus Torvalds
2007-07-16 6:19 ` Shawn O. Pearce
2007-07-15 21:56 ` Robin Rosenberg
2007-07-15 23:21 ` Robin H. Johnson
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=7vd4ytebsw.fsf@assigned-by-dhcp.cox.net \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=mhagger@alum.mit.edu \
--cc=seanlkml@sympatico.ca \
--cc=spearce@spearce.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.