From: Joel Becker <Joel.Becker@oracle.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: git-commit: allow From: line to be entered in commit message
Date: Thu, 12 Jan 2006 22:58:55 -0800 [thread overview]
Message-ID: <20060113065855.GJ14196@ca-server1.us.oracle.com> (raw)
In-Reply-To: <7vhd89mc0y.fsf@assigned-by-dhcp.cox.net>
On Thu, Jan 12, 2006 at 12:22:53PM -0800, Junio C Hamano wrote:
> Committing somebody else's changes by hand ought to be a rare
> event. Otherwise that is an indication that there needs to be a
>...
> Most of the time when I use "git commit", I'll be committing my
> own changes; I do not want to see "From: me" every time I
> commit.
Well, I'm wary of putting
GIT_AUTHOR_EMAIL=joel.becker@oracle.com as a permanent part of my
environment, for fear of overriding some other authors at some point.
On the other hand, if I don't put it in the environment, I get a bogus
author line (jlbec@thisbox.oracle.com). So I end up having to
hand-write the AUTHOR_EMAIL lines on each commit line; not a solution
I'm happy with.
This way, I'd have a chance to edit it and be sure :-)
Joel
--
Life's Little Instruction Book #274
"Leave everything a little better than you found it."
Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker@oracle.com
Phone: (650) 506-8127
next prev parent reply other threads:[~2006-01-13 6:59 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
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 [this message]
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=20060113065855.GJ14196@ca-server1.us.oracle.com \
--to=joel.becker@oracle.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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.