[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnu-arch-users] [BUG] feature plan -- downstream branches

From: Mikhael Goikhman
Subject: Re: [Gnu-arch-users] [BUG] feature plan -- downstream branches
Date: Tue, 25 May 2004 13:18:54 +0000
User-agent: Mutt/

On 25 May 2004 09:41:41 +0200, Florian Weimer wrote:
> * Tom Lord:
> > The ':' character should be permitted in branch names but
> > have a slightly special meaning.
> I don't think ":" is a permitted file name character on Windows.

How about a comma then, looks even nicer to me, tla--devo,ssh,bugs--1.3.

Of course, some may argue that the whole naming scheme is not good, and
branch name like tla--1.3--devo--ssh--bugs (or tla--devo--1.3--ssh--bugs)
is more hierarchy-correct. (Leaving aside all compatibility issues.)

Personally I may live with either scheme, but the issue of micro/macro
branch naming schemes seems to return often. One of the simple and
powerful solutions for the future may be to switch to 4-level branches,
category--macrobranch--version--microbranch with optional "macrobranch"
and "microbranch" parts. So 'tla fork' may by default extend/add the
"microbranch" part, but may also extend/add the "macrobranch" part
instead given an option. I.e. by default:

      # now in tla--devo--1.3            --patch-123

  % tla fork ssh

      # now in tla--devo--1.3--ssh       --base-0

  % tla fork bugs

      # now in tla--devo--1.3--ssh,bugs  --base-0


reply via email to

[Prev in Thread] Current Thread [Next in Thread]