info-cvs
[Top][All Lists]
Advanced

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

RE: matching a tag to a branch


From: Arthur Barrett
Subject: RE: matching a tag to a branch
Date: Sun, 4 Mar 2012 17:48:19 +1100

Jim,
 
Sorry - you misunderstand me I think.
 
The manual says that -r should work.  If you are saying it's not
working, then it's open source and you can fix it.  Or find a more
recent release where it is working.
 
Note: it's the server that generates tohe log, not the client, so the
server code is what is important here.
 
If it's not working in CVSNT 2.8 (yes it runs on linux servers, and hpux
servers and...)  then you should report it to the technical support team
and they can get it fixed, but I've already tested CVSNT and it works
(at least in my case).
 
Regards,
 
 
Arthur
 

        -----Original Message-----
        From: Jim Perrier [mailto:address@hidden 
        Sent: Friday, 2 March 2012 11:37 PM
        To: Arthur Barrett
        Cc: cvs-user-list
        Subject: Re: matching a tag to a branch
        
        
        Here is a sample of what's returned. I've cut out many of the
entries between " revisions with a zero as the second last character".
The tag was actually applied against DSC_5_0_R1.
        
        cvs log -hr:DSC_5_0_I112 | more
        cvs log: Logging tpapps
        
        RCS file: /swdev/tagcvs/tpapps/.IBUILD,v
        Working file: tpapps/.IBUILD
        head: 1.771
        branch:
        locks: strict
        access list:
        symbolic names:
                DSC_4_0_I834: 1.649.2.68
                DSC50LINUX: 1.739.0.2
                DSC_5_0_I80: 1.739
                DSC_4_0_I717: 1.649.2.33.2.9
                DSC50SANDBOX: 1.699.0.2
                DSC_5_0_I40: 1.699
                DSC_4_0_I800: 1.649.2.34
                DSC40R3: 1.649.2.33.0.2
                DSC_5_0_I36: 1.695
                DSC_4_0_R1-00: 1.623.2.17.2.1
                DSC40R1: 1.623.2.17.0.2
                DSC_4_0_I666: 1.640
        etc...
         
        On 3/2/2012 7:09 AM, Arthur Barrett wrote: 

                Jim,
                
                If you use the command I sent, you should just see the
branch(es) that
                tag is on.
                
                Regards,
                
                
                Arthur
                
                

                        -----Original Message-----
                        From: 
        
address@hidden 
        
[mailto:address@hidden
                        org] On Behalf Of Jim Perrier
                        Sent: Thursday, 1 March 2012 12:11 AM
                        To: cvs-user-list
                        Subject: Re: matching a tag to a branch
                        
                        
                        Sorry about the direct reply. You're right about
the zero as 
                        the second 
                        character. The only problem is that it returns
all the branches, not 
                        just the one ABC_1_0_I333 was created on. My
search for the correct 
                        wheel continues.
                        
                        \Jim
                        
                        
                        
                        On 2/22/2012 7:29 PM, Arthur Barrett wrote:

                                Hi Jim,
                                Please send questions to the group, not
direct to me.
                                My idea was not so much to use a GUI
tool, as in use the 

                        code that the 

                                GUI tool uses.  The point of open source
software is to 

                        reuse the code...

                                I tested this on CVSNT 2.8:
                                cvs log -hr:ABC_1_0_I333
                                If you search the output for revisions
with a zero as the 

                        second last 

                                character, you'll get the branches that
ABC_1_0_I333 is on.
                                Regards,
                                Arthur

                        



reply via email to

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