git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git-commit feature request: pass editor command line options

From
Miklos Vajna <vmiklos@frugalware.org>
Date
Oct 14, 2009, 22:12 UTC
Message-ID
<20091014221216.GI6115@genesis.frugalware.org>
In-Reply-To
<200910141303.01485.matt@nightrealms.com>
On Wed, Oct 14, 2009 at 01:03:01PM -0700, Matthew Cline <matt@nightrealms.com> wrote:
Show 7 quoted lines
> On Wednesday 14 October 2009 10:23:38 am Miklos Vajna wrote:
> 
> > Hmm, what is the use-case when using an option --foo is useful when
> > creating a commit, but not useful when crating a tag?
> 
> In my case, it's using a commit template which starts with a comment, so I 
> want to move the cursor down to the line below the comment.

Then rebase, tag, add -e and even commit --amend would use core.editor, while commit alone would use commit.editor, right?

A minor confusion would be that git commit --amend would not use commit.editor. ;-)

Previous: Matthew Cline
Message 6 of 6 in “git-commit feature request: pass editor command line options”
  1. Matthew ClineOct 14, 2009
  2. Miklos VajnaOct 14, 2009
  3. Junio C HamanoOct 14, 2009
  4. Jeff KingOct 14, 2009
  5. Matthew ClineOct 14, 2009
  6. Miklos VajnaOct 14, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.