All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Wong <normalperson@yhbt.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Sean <seanlkml@sympatico.ca>,
	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 20:35:41 -0700	[thread overview]
Message-ID: <20070716033540.GB29521@muzzle> (raw)
In-Reply-To: <7vd4ytebsw.fsf@assigned-by-dhcp.cox.net>

Junio C Hamano <gitster@pobox.com> wrote:
> Sean <seanlkml@sympatico.ca> writes:
> >> 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).

git-svn can do this, too.

I don't use it myself, but I remember the file format is the
same as the one git-svnimport and git-cvsimport use.

-- 
Eric Wong

  reply	other threads:[~2007-07-16  3:35 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
2007-07-16  3:35     ` Eric Wong [this message]
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=20070716033540.GB29521@muzzle \
    --to=normalperson@yhbt.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --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.