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

Using two-dot range notation in `git rebase`?

From
Philip Oakley <philipoakley@iee.email>
Date
Jul 28, 2021, 15:38 UTC
Message-ID
<b3b5f044-8c76-ec71-45d6-1c7fea93c519@iee.email>

Is there a reasonable way to use the two-dot range notation in git rebase, particularly in an  --onto situation?

In my case I have a short series that depends on both some existing Git for Windows (GfW) patches (`main` branch), and some patches now in `git/master`. I'm now able to rebase it onto the GfW `shears/master` branch which contains both sets of patches (and one that was in the last git release).

It felt that it ought to be possible to use a simple two dot range to extract my series, rather than identifying the individual end points in a similar manner to that used in the description"set of commits .. shown by `git log <upstream>..HEAD`".

Or is this something that could be a project? --

Philip
Next: Daniel Knittl-Frank
Message 1 of 10 in “Using two-dot range notation in `git rebase`?”
  1. Philip OakleyJul 28, 2021
  2. Daniel Knittl-FrankJul 28, 2021
  3. Philip OakleyJul 29, 2021
  4. Jeff KingJul 29, 2021
  5. Philip OakleyJul 29, 2021
  6. Junio C HamanoJul 29, 2021
  7. Sergey OrganovJul 29, 2021
  8. Junio C HamanoJul 29, 2021
  9. Jeff KingJul 29, 2021
  10. Junio C HamanoJul 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.