FW: Symbolic tag information after a 'cvs release'

[John Conti]

Hmm, Maybe this reply does not address the original post.
 
I think the reason why *release* was in quotes is to not imply the
release command but rather an individual's "release" process.  I too am
interested in how to expand a label or symbolic tag into a file.  This
would be handy for building tags and making them available for download
from a script.  This is what I do when I "release" software.
 
,John

        -----Original Message----- 
        From: Kaz Kylheku 
        Sent: Sat 4/6/2002 7:56 PM 
        To: Sonam Chauhan 
        Cc: address@hidden 
        Subject: Re: Symbolic tag information after a 'cvs release'
        
        

        On Sun, 7 Apr 2002, Sonam Chauhan wrote:
        
        > Date: Sun, 07 Apr 2002 00:00:03 +1000
        > From: Sonam Chauhan <address@hidden>
        > To: address@hidden
        > Subject: [info-cvs] Symbolic  tag information after a 'cvs
release'
        >
        > When 'releasing' a cvs module, is it possible to output the
symbolic tag of the
        > current release to a disk file? (the obvious choice would be
using placeholder
        
        What? ``Symbolic tag of the current release'' isn't a CVS
concept;
        there is no notion of a current release. That is an ontology
which you
        impose on your tags, usually by applying some kind of software
release
        process.
        
        The (perhaps ill-named) cvs release command implements a
discipline for
        destroying a checked out copy. It has nothing to do with making
a
        software release.
        
        --
        Meta-CVS: solid version control tool with directory structure
versioning.
        http://users.footprints.net/~kaz/mcvs.html
http://freshmeat.net/projects/mcvs
        
        
        _______________________________________________
        Info-cvs mailing list
        address@hidden
        http://mail.gnu.org/mailman/listinfo/info-cvs