git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felipe Contreras <felipe.contreras@gmail.com>
To: Kristian Freed <kristian.freed@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: How can I automatically create a GIT branch that represents a sequence of tags?
Date: Sun, 11 Aug 2013 05:16:29 -0500	[thread overview]
Message-ID: <CAMP44s1_rUVt9a6GbKFc7b0OjNtq4cZzSqC+i_s1k0x+Zs08UQ@mail.gmail.com> (raw)
In-Reply-To: <CAFw3YtRLgUGGn9JV5K3P9XtMBcBeO7=VSM7PekSxtW6xCsfZ1Q@mail.gmail.com>

On Sat, Aug 10, 2013 at 5:29 PM, Kristian Freed
<kristian.freed@gmail.com> wrote:
> 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

      parent reply	other threads:[~2013-08-11 10:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-10 22:29 How can I automatically create a GIT branch that represents a sequence of tags? Kristian Freed
2013-08-10 23:20 ` Fredrik Gustafsson
2013-08-11  5:16   ` Michael Haggerty
2013-08-11  6:20     ` Fredrik Gustafsson
2013-08-11  7:49   ` Philip Oakley
2013-08-11 11:13   ` Kristian Freed
2013-08-11 12:23     ` Fredrik Gustafsson
2013-08-11  9:36 ` Andreas Schwab
2013-08-11 10:16 ` Felipe Contreras [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAMP44s1_rUVt9a6GbKFc7b0OjNtq4cZzSqC+i_s1k0x+Zs08UQ@mail.gmail.com \
    --to=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=kristian.freed@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).