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

Re: [PATCH] Avoid warning when bisecting a merge

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 5, 2008, 08:31 UTC
Message-ID
<7v3akfvvsp.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<48C0DD32.5010008@isy.liu.se>
Gustaf Hendeby <hendeby@isy.liu.se> writes:
Show 7 quoted lines
> On 09/05/2008 08:29 AM, Junio C Hamano wrote:
> ...
>> Yup, that might make more sense. In the meantime, I suspect this makes
>> more sense than introducing a new state "0".
>
> I can't argue with that.  Junio, your suggestion makes more sense.  I
> should have paid more attention to what I was doing.  Sorry about the noise.

That's Ok. Spotting mistakes is an important part of the review process; there is no need to be afraid of or apologetic about it.

Previous: Gustaf Hendeby
Message 5 of 5 in “Avoid warning when bisecting a merge”
  1. Avoid warning when bisecting a mergeGustaf Hendeby, Sep 4, 2008
  2. Christian CouderSep 5, 2008
  3. Junio C HamanoSep 5, 2008
  4. Gustaf HendebySep 5, 2008
  5. Junio C HamanoSep 5, 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.