From: Andreas Ericsson <ae@op5.se>
To: git@vger.kernel.org
Subject: Re: [PATCH] git-cvsimport: Add -A <author-conv-file> option
Date: Fri, 13 Jan 2006 03:14:27 +0100 [thread overview]
Message-ID: <43C70D03.4040609@op5.se> (raw)
In-Reply-To: <7vvewohoy0.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> ISTR there was a thread that suggested using CVSROOT/users file
> for this purpose.
>
> http://thread.gmane.org/gmane.comp.version-control.git/8167
>
ISTR?
That patch doesn't work when importing from sourceforge (among others),
because no-one uses their devname@users.sourceforge.net address (and
often just filter them out because they attract so much spam). It also
does nothing for when the username isn't the leading part of the
email-addres, or for GIT_AUTHOR_NAME, which is the most disturbing since
it ruffles the shortlog output. We use that shortlog to get a gisted
changelog for the sales and marketing people. I can recommend this.
They're absolutely thrilled to see things like "Only use vararg macros
#ifdef __GNUC__" and "declare **envp const throughout mplex api". ;)
Anyways, I can keep this separate if you don't want to accept it. I'll
most likely implement some config-reading to it too though so I don't
have to type the repository name and such each time I run it.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
next prev parent reply other threads:[~2006-01-13 2:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-12 23:38 [PATCH] git-cvsimport: Add -A <author-conv-file> option Andreas Ericsson
2006-01-13 1:55 ` Junio C Hamano
2006-01-13 2:14 ` Andreas Ericsson [this message]
2006-01-13 4:09 ` Junio C Hamano
2006-01-13 8:45 ` Junio C Hamano
2006-01-13 3:19 ` Alexander Litvinov
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=43C70D03.4040609@op5.se \
--to=ae@op5.se \
--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.
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).