git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: sean <seanlkml@sympatico.ca>
To: Junio C Hamano <junkio@cox.net>
Cc: greenkaa@gmail.com, git@vger.kernel.org
Subject: Re: git-commit: allow From: line to be entered in commit message
Date: Fri, 13 Jan 2006 12:54:04 -0500	[thread overview]
Message-ID: <BAYC1-PASMTP0918AE856AD34E35597CA4AE260@CEZ.ICE> (raw)
Message-ID: <20060113125404.58c4ce30.seanlkml@sympatico.ca> (raw)
In-Reply-To: <7v64oo9gc7.fsf@assigned-by-dhcp.cox.net>

On Fri, 13 Jan 2006 09:40:24 -0800
Junio C Hamano <junkio@cox.net> wrote:

> Have you two known that more than one environment variables can
> be set for one-shot command execution?
> 
> 	$ GIT_AUTHOR_NAME="$author" \
> 	  GIT_AUTHOR_EMAIL="$email" git commit -F .msgfile
> 
> would give these environment variables for this "git commit"
> without affecting the later commands.

No, I didn't know that; thanks for the lesson.

> 
> Not that this really matters, since the above example was an
> excerpt of my suggestion about how to do this in a script,
> somehow made to look as if it was a suggestion about running
> things by hand from the command line...
> 

I said quite a few times now this has nothing to do with running
git-commit from a script.   This is just a simple request
to not require the use of environment variables to pass useful
parameters.

I really don't understand your gripe on this one, when someone 
else suggested using a command line parameter for author
information you said:

<quote>

> 	--from="Some User <some.user@theoffice.org>"
>

I agree this would be more useful, direct, easy to understand
and explain way to do it.

</quote>


So do you still agree with that, would you accept a patch?  Or do you have
some fundamental reason to think that environment variables are a better
way to pass information in this case?

Cheers,
Sean

  reply	other threads:[~2006-01-13 17:58 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060112093700.1d3d25db.seanlkml@sympatico.ca>
2006-01-12 14:37 ` git-commit: allow From: line to be entered in commit message sean
     [not found]   ` <20060112102123.581e373e.seanlkml@sympatico.ca>
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
     [not found]       ` <20060112214307.174f5719.seanlkml@sympatico.ca>
2006-01-13  2:43         ` sean
     [not found]     ` <20060112213207.05d76b28.seanlkml@sympatico.ca>
2006-01-13  2:32       ` sean
2006-01-13  4:03         ` Junio C Hamano
     [not found]           ` <20060112230633.0858694a.seanlkml@sympatico.ca>
2006-01-13  4:06             ` sean
2006-01-13  4:35               ` Junio C Hamano
     [not found]                 ` <20060112235103.42665813.seanlkml@sympatico.ca>
2006-01-13  4:51                   ` sean
2006-01-13 11:11                     ` Artem Khodush
2006-01-13 17:40                       ` Junio C Hamano
     [not found]                         ` <20060113125404.58c4ce30.seanlkml@sympatico.ca>
2006-01-13 17:54                           ` sean [this message]
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
     [not found]   ` <20060112214642.3c88282c.seanlkml@sympatico.ca>
2006-01-13  2:46     ` sean
2006-01-13  3:58       ` Junio C Hamano
     [not found]         ` <20060112225800.411a04c1.seanlkml@sympatico.ca>
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=BAYC1-PASMTP0918AE856AD34E35597CA4AE260@CEZ.ICE \
    --to=seanlkml@sympatico.ca \
    --cc=git@vger.kernel.org \
    --cc=greenkaa@gmail.com \
    --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 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).