[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: RFC: CHANGES

From: <cmpilato_at_collab.net>
Date: 2003-02-19 19:10:49 CET

Michael Price <mprice@atl.lmco.com> writes:

> cmpilato@collab.net writes:
> > > Anyone wise in the ways of dist.sh-foo who has a free moment please let
> > > me know.
> >
> > Whatcha need?
>
> Well, my impression of the first few commits was as follows:
>
> 1. Get the go ahead to bump the version number and commit CHANGES.
> 2. Copy HEAD to branches/0.18
> 3. Use dist.sh to create the tarball.
> 4. Fix bugs on branch.
> 5. Go back to step 3 as needed.
> 6. Merge relevant changes to trunk if needed.
> 7. Copy branches/0.18 to tags/0.18.
> 8. Remove branch if its no longer needed.
>
> So, when I'm running dist.sh, if I specify the branch (branches/0.18) as
> the REPOS-PATH then do I specify the VERSION from the commit in #1 above
> or do I use some other revision number?

You can specify "HEAD" as the version, so:

   ./dist.sh HEAD '' branches/0.18

Is (I think) what you want. That script has grown so many nasty
band-aids, it's ridiculous. The whole thing should be converted to a
real scripting language with get-opt support so that we can do:

   ./dist.py --revision HEAD --path branches/0.18

and let the tarball name be derived with the '' cmd-line padding.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Feb 19 19:12:25 2003

This is an archived mail posted to the Subversion Dev mailing list.