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

Re: Feature request: Keyword $Rev$ with a twist

From: Josef Wolf <jw_at_raven.inka.de>
Date: 2002-08-08 23:41:43 CEST

On Thu, Aug 08, 2002 at 02:07:43PM +0200, Mats Nilsson wrote:
> Josef Wolf [mailto:jw@raven.inka.de] writes:
> >
> > What would be wrong with the $HeadURL$-solution I posted on this
> > thread?
>
> Sorry - I must have missed the post.
>
> I just went back and reread the thread. The proposal is to always create a
> tag for each important build, and build from that tag and then use
> $HeadURL$. Since tags are logically read-only, $Rev$ or $WorkingRev$ offers
> no extra information. $HeadURL$ says it all.

Exactly.

> Given these premises, nothing is wrong with this idea. As far as I'm
> concerned, I'm happy with it, assuming that it is straigtforward to
> construct a pre commit hook that rejects every kind of commit except a
> non-replacing copy directly to the tags root.
>
> Two more or less obvious minor comments:
> * If tags are not read-only, someone may change or replace the tag contents,
> and this system breaks.

As I wrote in the original mail, that was just a rough Idea how I plan
to run my repositories. Thanks for your remarks. Such a solution would
definitely need some protection against rewriting tagged data.

> * In most other circumstances using svn there is always a choice between
> tagging and refering to the tag, or use the URL and rev. In this case
> however, the URL+rev is not available.

Hmm, did not get this one. Could you please increase verbosity?

-- 
-- Josef Wolf -- jw@raven.inka.de --
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Aug 8 23:42:39 2002

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.