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

git tag --contains for cherry-picks

From
Laszlo Papp <lpapp@kde.org>
Date
Jun 29, 2016, 11:48 UTC
Message-ID
<CAOMwXhNp9SwA_oQ8bE6-m72C+po+28maGtsP8wRFRfBLjSb5NA@mail.gmail.com>
Dear List,

We have several release branches as well as a master branch where the active development happens.

Old releases are maintained with important bug fixes or even new features in our case. It sometimes means that we need to cherry-pick commits across branches, like from master to a specific release branch.

Cherry-picking changes the hash of the commit, therefore, this may no longer work for cherry-picks:

git tag --contains
I am thinking of having something like:
git tag --contains-follow

which would follow cherry-picks. I am not sure how easily and/or efficiently this can be implemented, but my gut feeling is that in the vast majority of the cases, the content check would bail out already at the "subject line".

Again, just to recap: I would like to be able to list of releases (i.e. tags) in which a commit occurs even if it is cherry-picked because what matters for us in the end of the day is whether the feature or bugfix goes into a release.

Best Regards, Laszlo Papp

Next: Jeff King
Message 1 of 3 in “git tag --contains for cherry-picks”
  1. Laszlo PappJun 29, 2016
  2. Jeff KingJun 30, 2016
  3. Jakub NarębskiJun 30, 2016

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.