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