From: Andreas Ericsson <ae@op5.se>
To: Junio C Hamano <junkio@cox.net>
Cc: sean <seanlkml@sympatico.ca>, git@vger.kernel.org
Subject: Re: git-commit: allow From: line to be entered in commit message
Date: Thu, 12 Jan 2006 22:53:09 +0100 [thread overview]
Message-ID: <43C6CFC5.5010902@op5.se> (raw)
In-Reply-To: <7vzmm1mcfz.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
>
> If you typed that line, why somebody else's change ended up in
> your working tree is a mystery to me, but let's say an
> office-mate edited things for you and said "this should work.
> test it out and if it is OK commit it for me." I have seen this
> kind of thing done in real life.
>
This happens from time to time where I work, but I think it would be
more useful to have
--from="Some User <some.user@theoffice.org>"
which would save even more typing.
I had thought of coupling this with some translation-scheme thingie, so
that "--from=jd" would be automagically converted to the proper name and
email address. I first came to think about this when I imported most of
our projects from CVS, but I ended up doing a quick-hack to
git-cvsimport instead.
--
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-12 21:53 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-12 14:37 git-commit: allow From: line to be entered in commit message sean
2006-01-12 14:37 ` sean
2006-01-12 15:21 ` sean
2006-01-12 15:21 ` sean
2006-01-12 20:13 ` Junio C Hamano
2006-01-12 21:53 ` Andreas Ericsson [this message]
2006-01-12 22:15 ` Junio C Hamano
2006-01-13 2:43 ` sean
2006-01-13 2:43 ` sean
2006-01-13 2:32 ` sean
2006-01-13 2:32 ` sean
2006-01-13 4:03 ` Junio C Hamano
2006-01-13 4:06 ` sean
2006-01-13 4:06 ` sean
2006-01-13 4:35 ` Junio C Hamano
2006-01-13 4:51 ` sean
2006-01-13 4:51 ` sean
2006-01-13 11:11 ` Artem Khodush
2006-01-13 17:40 ` Junio C Hamano
2006-01-13 17:54 ` sean
2006-01-13 17:54 ` sean
2006-01-13 19:51 ` Junio C Hamano
2006-01-13 21:53 ` Johannes Schindelin
2006-01-12 19:00 ` Joel Becker
2006-01-12 20:22 ` Junio C Hamano
2006-01-13 6:58 ` Joel Becker
2006-01-13 7:06 ` Junio C Hamano
2006-01-13 19:12 ` Joel Becker
2006-01-13 19:39 ` Junio C Hamano
2006-01-13 20:01 ` Joel Becker
2006-01-13 20:33 ` Junio C Hamano
2006-01-13 20:46 ` Junio C Hamano
2006-01-13 21:47 ` Johannes Schindelin
2006-01-12 20:16 ` Alex Riesen
2006-01-13 2:46 ` sean
2006-01-13 2:46 ` sean
2006-01-13 3:58 ` Junio C Hamano
2006-01-13 3:58 ` sean
2006-01-13 3:58 ` sean
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=43C6CFC5.5010902@op5.se \
--to=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=seanlkml@sympatico.ca \
/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.