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

Re: How can I automatically create a GIT branch that represents a sequence of tags?

From
Felipe Contreras <felipe.contreras@gmail.com>
Date
Aug 11, 2013, 10:16 UTC
Message-ID
<CAMP44s1_rUVt9a6GbKFc7b0OjNtq4cZzSqC+i_s1k0x+Zs08UQ@mail.gmail.com>
In-Reply-To
<CAFw3YtRLgUGGn9JV5K3P9XtMBcBeO7=VSM7PekSxtW6xCsfZ1Q@mail.gmail.com>

On Sat, Aug 10, 2013 at 5:29 PM, Kristian Freed <kristian.freed@gmail.com> wrote:

Show 8 quoted lines
> In our current setup, we have automatic tagging in git of all
> successful release builds. This makes it easy to go back to stable
> points in history and compare functionality, check when bugs were
> introduced etc.
>
> To help with this process further, it would be useful to be able to
> use git bisect, but as these are just a sequence of tags, not commits
> on a branch, git bisect will not work as is.
Why don't you just do 'git bisect skip' if the commit doesn't have a tag?
> Is there any tooling for automatically recreating a branch from a
> sequence of tags, where each generated commit is the calculated delta
> between each two neighbouring tags?
That would probably involve listing the wanted tags:
% git log --topo-order --simplify-by-decoration --decorate --oneline
And then generating the commits:

% git cat-file -p v1.8.3 > commit # modify commit's parent % git hash-object -w < commit

-- 
Felipe Contreras
Previous: Andreas Schwab
Message 9 of 9 in “How can I automatically create a GIT branch that represents a sequence of tags?”
  1. Kristian FreedAug 10, 2013
  2. Fredrik GustafssonAug 10, 2013
  3. Michael HaggertyAug 11, 2013
  4. Fredrik GustafssonAug 11, 2013
  5. Philip OakleyAug 11, 2013
  6. Kristian FreedAug 11, 2013
  7. Fredrik GustafssonAug 11, 2013
  8. Andreas SchwabAug 11, 2013
  9. Felipe ContrerasAug 11, 2013

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.