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

Re: 'next' will be rewound shortly

From
Stephan Beyer <s-beyer@gmx.net>
Date
Jun 27, 2008, 23:41 UTC
Message-ID
<20080627234104.68810@gmx.net>
In-Reply-To
<20080627213605.GD2058@genesis.frugalware.org>
Hi,
Show 9 quoted lines
> <gitster@pobox.com> wrote:
> > Following git tradition, manpage came after the command's behaviour has
> > been long established.  It will be a behaviour change, and it is open to
> > debate if the new behaviour is better or if the proposed change of
> > behaviour hurts existing users.
> 
> If my opinion counts, I like the current ("prepend") one, and I think
> the best would be to add a new option (and/or make it configurable) for
> the new ("replace") one.
Well, perhaps I am different, but I sometimes have temporary branches
named like "first-silly-experiment" and I do not expect having a
    Merge branch 'another-silly-experiment' into 'first-silly-experiment'
appended, when I do a
    git merge -m "Merge a lot of useful stuff... blabla" another-silly-experiment.
(btw, I don't *really* name my branches like this..it's just an example.)
Well, I see this from a "sequencer author point of view", where
     merge silly-experiment
will invoke an editor,
     merge --standard silly-experiment
generates some kind of the typical standard (or default) message,
and
     merge --message "Merge blabla" silly-experiment
does the "obvious". (For me this is the obvious since I've never
experienced another behavior. All my merges have been using the
now disappeared commit.)

So I'd vote for a "replace" behavior by default on -m, and an "append standard message" option, but if there is *one* person who relies on the prepend feature, I'd also take the "prepend" default and would like to vote for an option that does the replacement.

For the current state of the art, it seems that I have to merge with whatever message and then do a commit -m "..." --amend.

Regards,
  Stephan Beyer
PS: Currently using webmail. So sorry for any too long lines
or whatever.
-- 
GMX startet ShortView.de. Hier findest Du Leute mit Deinen Interessen!
Jetzt dabei sein: http://www.shortview.de/wasistshortview.php?mc=sv_ext_mf@gmx
Previous: Miklos VajnaNext: Junio C Hamano
Message 10 of 15 in “[ANNOUNCE] GIT 1.5.6”
  1. Junio C HamanoJun 18, 2008
  2. A note from the maintainerJunio C Hamano, Jun 19, 2008
  3. 'next' will be rewound shortlyJunio C Hamano, Jun 19, 2008
  4. Stephan BeyerJun 27, 2008
  5. Miklos VajnaJun 27, 2008
  6. Stephan BeyerJun 27, 2008
  7. Miklos VajnaJun 27, 2008
  8. Junio C HamanoJun 27, 2008
  9. Miklos VajnaJun 27, 2008
  10. Stephan BeyerJun 27, 2008
  11. Junio C HamanoJun 28, 2008
  12. A note from the maintainerJunio C Hamano, Jul 14, 2008
  13. Steffen ProhaskaJun 22, 2008
  14. [ANNOUNCE] GIT 1.5.6.1Junio C Hamano, Jun 26, 2008
  15. Steffen ProhaskaJul 1, 2008

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.