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

RE: Regression in git-subtree.sh, introduced in 2.20.1, after 315a84f9aa0e2e629b0680068646b0032518ebed

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Jan 3, 2019, 13:50 UTC
Message-ID
<nycvar.QRO.7.76.6.1901031448260.45@tvgsbejvaqbjf.bet>
In-Reply-To
<59718f73a0a14b828a6d4fd4c8c222d1@MBX260.adm.swri.edu>
Hi Roger,
On Wed, 2 Jan 2019, Strain, Roger L. wrote:
> TL;DR: Current script uses git rev-list to retrieve all commits which
> are reachable from HEAD but not from <abc123>. Is there a syntax that
> will instead return all commits reachable from HEAD, but stop traversing
> when <abc123> is encountered? It's a subtle distinction, but important.

Maybe you are looking for the --ancestry-path option? Essentially, `git rev-list --ancestry-path A..B` will list only commits that are reachable from B, not reachable from A, but that *can* reach A (i.e. that are descendants of A).

Ciao, Johannes

Previous: Strain, Roger L.Next: Strain, Roger L.
Message 11 of 12 in “Regression in git-subtree.sh, introduced in 2.20.1, after 315a84f9aa0e2e629b0680068646b0032518ebed”
  1. Marc BalmerDec 31, 2018
  2. Duy NguyenDec 31, 2018
  3. Marc BalmerDec 31, 2018
  4. Duy NguyenDec 31, 2018
  5. Marc BalmerDec 31, 2018
  6. Duy NguyenDec 31, 2018
  7. Marc BalmerDec 31, 2018
  8. Duy NguyenJan 1, 2019
  9. Marc BalmerJan 2, 2019
  10. Strain, Roger L.Jan 2, 2019
  11. Johannes SchindelinJan 3, 2019
  12. Strain, Roger L.Jan 3, 2019

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.