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

Re: [PATCH 2/2] bash: not all 'git bisect' subcommands make sense when not bisecting

From
Sverre Rabbelier <srabbelier@gmail.com>
Date
Oct 10, 2010, 22:05 UTC
Message-ID
<AANLkTi==oCKgw86fy6sPiPuKuownsbob3xXiY=hHhYrQ@mail.gmail.com>
In-Reply-To
<1286746774-7877-2-git-send-email-szeder@ira.uka.de>
Heya,
On Sun, Oct 10, 2010 at 23:39, SZEDER Gábor <szeder@ira.uka.de> wrote:
> ... but only 'start' and 'replay'.  The other commands will either
> error out or offer to start bisecting for the user.

I'm not sure, following the same concept "git rebase" should not offer "--continue" if you're not rebasing. It might just be frustrating for the user since they might not realize they're not bisecting yet.

-- 
Cheers,

Sverre Rabbelier
Previous: SZEDER GáborNext: SZEDER Gábor
Message 3 of 5 in “bash: offer refs for 'git bisect start'”
  1. 1/2 bash: offer refs for 'git bisect start'SZEDER Gábor, Oct 10, 2010
  2. 2/2 bash: not all 'git bisect' subcommands make sense when not bisectingSZEDER Gábor, Oct 10, 2010
  3. Sverre RabbelierOct 10, 2010
  4. SZEDER GáborOct 10, 2010
  5. Sverre RabbelierOct 10, 2010

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.