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

Re: [PATCH] git-rebase documentation: explain the exit code of custom commands

From
Stefan Beller <sbeller@google.com>
Date
Dec 30, 2014, 19:36 UTC
Message-ID
<CAGZ79kZ8WgR2SxnX9TheUhpJqX50OhTGOi-jnjw5TDySyr4YWg@mail.gmail.com>
In-Reply-To
<CAGZ79kZsQpvNzGPYuS64Cx2hFoozcb2HxU9Chd1__5=kkE-WjQ@mail.gmail.com>
On Tue, Dec 30, 2014 at 10:25 AM, Stefan Beller <sbeller@google.com> wrote:
Show 5 quoted lines
> Should this be s/current/previous/. Technically the current commit seems
> correct to me, but it was crafted in the previous lines of the instruction sheet
> so it feels like it's a commit which is already done and we're
> currently looking at the
> commit which should be squashed into the HEAD.
This would also support consistency with the help given in the
instruction sheet.
    #  s, squash = use commit, but meld into previous commit
Previous: Stefan BellerNext: Junio C Hamano
Message 4 of 5 in “git-rebase documentation: explain the exit code of custom commands”
  1. git-rebase documentation: explain the exit code of custom commandsStefan Beller, Dec 29, 2014
  2. Junio C HamanoDec 30, 2014
  3. Stefan BellerDec 30, 2014
  4. Stefan BellerDec 30, 2014
  5. Junio C HamanoDec 30, 2014

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.