Re: branch versioning

From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Date: Oct 4, 2010, 13:50 UTC
Message-ID: <AANLkTinR31x9NrsHoDt3UQ8w=hioPGtkQDkQ-5bSNW69@mail.gmail.com>
In-Reply-To: <AANLkTi=73Siu9O1WT8MdjfAEO5j5y=CkOAiof0z83L=c@mail.gmail.com>

On 10/4/10, Ævar Arnfjörð Bjarmason <avarab@gmail.com> wrote:

Show 11 quoted lines

> On Mon, Oct 4, 2010 at 13:18, Nguyen Thai Ngoc Duy <pclouds@gmail.com> wrote:
>  > How do you guys manage versions of a topic branch? I usually end up
>  > saving format-patch series somewhere or forget all old versions.
>  > Although I really want to keep old versions around. reflog to me   is
>  > polluted with every kind of branch updates. And it's local
>  > information. It can't be transferred to another repo (or can it?)
>
>
> I usually have foo, foo-v2, foo-v3 which eventually gets reset back to
>  foo once I'm sure nobody cares about the initial one or foo-v2. It's
>  very chaotic.

You remind me of my ~100 patch rebase/refactor on busybox-w32. I had up to master.7 :)

Show 5 quoted lines

>  So my git.git on GitHub is up to 123 branches, and I don't even want
>  to know what my personal git.git is at. I also save my outgoing
>  format-patch E-Mails, but would probably do less of that if there was
>  support for attaching the comments after the diffstat in a git-note or
>  something.

OK. Thanks for the information. I'll try my best to stay away from your repo :-D. Seriously, how can you select a branch out of those 123 branches? Does git-branch support regex matching or.. (looked up git-branch.txt, no it does not)

-- 
Duy