(I forgot to send this to bug-cvs too.)

--- Stephen Cameron <[EMAIL PROTECTED]> wrote:
> Date: Thu, 8 Jun 2000 19:50:03 -0700 (PDT)
> From: Stephen Cameron <[EMAIL PROTECTED]>
> Subject: A branch-tag name for the trunk! maybe.  (was RE: diff bug when
> using HEAD)
> To: [EMAIL PROTECTED]
> 
> 
> [EMAIL PROTECTED] (that's me) wrote:
> 
> [smc]  "TRUNK" sounds useful, "HEAD" as 
>  described here, less so, since the branch
>  tag may currently be used for that purpose, 
>  (though it might be useful for scripts or
>  something that don't want to have to 
>  know what the branch tag is, or in the case
>  of some kind of hybrid sandbox with 
>  modules from multiple branches (or even
>  multiple repositorires?))
>  But, does anyone here know how to 
>  implement either HEAD or TRUNK as 
>  described here? ,, I don't know how.  
>  Well, perhaps someone does...  
>  
> Heck, perhaps *I* do, after all.  I've 
> implemented *something* anyway, a ".trunk"
> tag that acts very very much like a 
> branch tag for the trunk.  You can
> "cvs diff", "cvs add", "cvs remove",
> "cvs update", "cvs checkout", "cvs
> commit" using this tag.  Also it doesn't
> break the current behavior of "no tag 
> means the trunk".  "cvs update -A" will
> get rid of the sticky ".trunk pseudo
> branch tag" too, and "cvs update -r .trunk"
> will bring it back...
> 
> Anyway, you can check out my attempt
> at a patch here, if you have the inclination.
> 
> http://www.geocities.com/dotslashstar/branch_patch.html
> The patch is against the current (6/8/2000) development
> version of CVS.
> 
> The patch leaves the current (broken)
> behavior of HEAD as is, ".trunk" does
> what HEAD should have done, I think.
> 
> (There aren't any sanity.sh tests yet...
> and I haven't tried it in client server mode yet,
> and don't try this on a real repository yet, etc.
> etc.  I think it works, but I wouldn't want to
> ruin anybody's day with what could easily be
> shoddy code, you know?  Consider yourself
> warned.
> 
> There's some stuff there in commit.c that I 
> wasn't really too sure about..., but it seemed
> to work on the things that I tried...
> 
> -- steve
>


__________________________________________________
Do You Yahoo!?
Yahoo! Photos -- now, 100 FREE prints!
http://photos.yahoo.com

Reply via email to