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

Re: [RFC/PATCH] git-what: explain what to do next

From
Junio C Hamano <gitster@pobox.com>
Date
May 29, 2008, 05:09 UTC
Message-ID
<7vlk1tpug5.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<200805290639.38134.chriscool@tuxfamily.org>
Christian Couder <chriscool@tuxfamily.org> writes:
> It seems not very friendly to just "return 1" when not bisecting.
> And before my last patch to use BISECT_START to check if we are bisecting, 
> it would perhaps have been better to use 'test -f "$GIT_DIR/BISECT_NAMES"'.

The reason for this silence is because Santi wants to call potential culprits in turn and stop when one responds "Yeah, I am the guilty one who threw a monkey wrench into the user's workflow". For that to work, "No, the user is not in the middle of any interaction with me" response needs to be silent.

Previous: Christian CouderNext: Jon Loeliger
Message 13 of 14 in “git-what: explain what to do next”
  1. git-what: explain what to do nextSanti Béjar, May 27, 2008
  2. Johannes SchindelinMay 27, 2008
  3. Santi BéjarMay 27, 2008
  4. Johannes SchindelinMay 27, 2008
  5. Santi BéjarMay 27, 2008
  6. Stephen R. van den BergMay 27, 2008
  7. Santi BéjarMay 27, 2008
  8. Steven WalterMay 27, 2008
  9. Junio C HamanoMay 27, 2008
  10. Junio C HamanoMay 27, 2008
  11. Santi BéjarMay 28, 2008
  12. Christian CouderMay 29, 2008
  13. Junio C HamanoMay 29, 2008
  14. Jon LoeligerMay 29, 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.