From: Nico Williams <nico@cryptonector.com>
Date: Thu, 07 Aug 2014 22:59:25 GMT
Subject: Re: "Branch objects" (was: Re: cherry picking and merge)
Message-ID: <CAK3OfOgg3fwQ2KZyG-V6-gHaWknZN_Y9KxQWwRZGcUOo7yjg5w@mail.gmail.com>
In-Reply-To: <alpine.LSU.2.00.1408071222510.13901@hermes-1.csi.cam.ac.uk>

On Thu, Aug 7, 2014 at 6:38 AM, Tony Finch <dot@dotat.at> wrote:
> So I have a small tool which maintains a publication branch which tracks
> the head of a rebasing branch. It's reasonably satisfactory so far...
>
> https://git.csx.cam.ac.uk/x/ucs/git/git-repub.git
>
> ... though the structure of the publication branch is weird and not very
> easy to navigate. You can see it in action in my git.git repo:

You know, maybe you could even use this to automatically figure out
the merge base for downstreams that follow your rebased branch:
auto-generate the git rebase --onto <head> <head as it was prior to
all the upstream rebases>.

That would be awesome, particularly if integrated into git.  It would
then be fine to rebase published branches in most cases, for example.

Nico