All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joel Becker <Joel.Becker@oracle.com>
To: sean <seanlkml@sympatico.ca>
Cc: git <git@vger.kernel.org>
Subject: Re: git-commit: allow From: line to be entered in commit message
Date: Thu, 12 Jan 2006 11:00:31 -0800	[thread overview]
Message-ID: <20060112190031.GH14196@ca-server1.us.oracle.com> (raw)
In-Reply-To: <20060112093700.1d3d25db.seanlkml@sympatico.ca>

On Thu, Jan 12, 2006 at 09:37:00AM -0500, sean wrote:
> Use the author name and email information given as the 
> first line of the commit message in the form of:
> 
> From: name <email>
> 
> as the author's name and email address in the resulting
> commit object.  This makes committing foreign patches
> a little less cumbersome to handle for some workflows.

	If we do this, can we have it populated up front?  That is, when
the edit opens, the current idea of author is in the comments as "From:"
so I can see what the author would be if I changed nothing.  This would
catch surprises where I'd forgotten to set AUTHOR_*, etc.

Joel
 

-- 

Life's Little Instruction Book #182

	"Be romantic."

Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker@oracle.com
Phone: (650) 506-8127

  parent reply	other threads:[~2006-01-12 19:00 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 [this message]
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=20060112190031.GH14196@ca-server1.us.oracle.com \
    --to=joel.becker@oracle.com \
    --cc=git@vger.kernel.org \
    --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.