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

Re: [PATCH v4] t6030: add test for git bisect skip started with --term* arguments

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 29, 2021, 08:20 UTC
Message-ID
<xmqqim45h585.fsf@gitster.g>
In-Reply-To
<CAP8UFD23Wvm-SpoAoFZZWXfXO_KGPdT5vwa4gWXMbtgL66me=w@mail.gmail.com>
Christian Couder <christian.couder@gmail.com> writes:
Show 6 quoted lines
> I am not sure how safe it is to use the hash of a commit that is in
> seen but not yet in next. I suggested using "a previous commit"
> instead as I thought that both the fix and this commit should be part
> of the same branch, and then it would be obvious which commit it is.
> Maybe we should wait for Junio to come back from vacation and decide
> about this.

It is totally unsafe. Besides, I do not think it is worth to make the fix and the test as two separate commits---can I ask you to help coordinate co-authorship between Ramsay and Bagas to come up with a combined single patch?

Thanks.
Previous: Christian Couder
Message 3 of 3 in “t6030: add test for git bisect skip started with --term* arguments”
  1. t6030: add test for git bisect skip started with --term* argumentsBagas Sanjaya, Apr 29, 2021
  2. Christian CouderApr 29, 2021
  3. Junio C HamanoApr 29, 2021

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.