[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnu-arch-users] Re: how to best tag releases
From: |
Jan Hudec |
Subject: |
Re: [Gnu-arch-users] Re: how to best tag releases |
Date: |
Wed, 31 Mar 2004 11:18:18 +0200 |
User-agent: |
Mutt/1.5.5.1+cvs20040105i |
On Wed, Mar 31, 2004 at 01:02:55 +0000, Mark Stosberg wrote:
> On 2004-03-29, Aaron Bentley <address@hidden> wrote:
> > Mark Stosberg wrote:
> >
> >>
> >> Before now, I've been using 'tla tag', like my example below. I didn't
> >> like that
> >> I had explicitly give the revision I wanted to tag. I wanted a way to say
> >> something that would
> >> mean something like the "current tree revision" or "latest revision". (I
> >> was able to do that in CVS.)
> >
> > You can specify a version, not just a revision. The documentation is
> > out-of-date.
> >
> > So you can do this:
> > $ tla tag $(tla tree-version) $targetversion
> >
> > This will work as long as you want to tag from the latest revision of
> > the tree version.
>
> Thanks for the response.
>
> I have a point of clarification about this. Does this tag the /current/
> patch level or is it essentially tagging 'HEAD' (in CVS terms) so the
> tag will point to different code at different times? I want the former
> behavior.
NO! Sure not! It tags the current-at-the-time-of-tag version and the
"Continuation" log will contain the full revision. Just try to think
how a branch from moving base would work...
-------------------------------------------------------------------------------
Jan 'Bulb' Hudec
<address@hidden>
signature.asc
Description: Digital signature