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

Read-only tags mentioned in the handbook

From: Kirby C. Bohling <kbohling_at_birddog.com>
Date: 2002-09-26 17:46:33 CEST

The handbook makes of using cp to create a tag, or a branch.
Specifically, it says that everything is a directory, and that the only
difference between a tag and a branch is the human applied
interpretation. It then mentions, marking tags as "read-only". I
searched for the "read-only" in the handbook and failed to see how you
could mark a tag that way. I'm guessing it's either a property, or an
apache config issue?

The specific sentence is:

"Each time /projectA/trunk reaches a taggable state, make a copy of the
directory somewhere in /projectA/tags/, and set the copy to read-only.
Use the same procedure to create a branch in /projectA/branches/"

Which is in the "Branches and Tags" section.

Did I miss it in the documentation? Sorry if this is obviously in the
docs, but I didn't see it mentioned anywhere else in the handbook. I'm
curious about how you do this.

The only other pertinate information I found is here:

"To restrict write-access only, you need to require a valid user for all
request methods except those that are read-only:

<LimitExcept GET PROPFIND OPTIONS REPORT>
   Require valid-user
</LimitExcept>"

Would you just apply something like to to subdir's you plan on only
letting tags into? Just curious about how to actually enforce that a
tag can't be written to.

        
        Thanks,
                Kirby

-- 
Real Programmers view electronic multimedia files with a hex editor.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Sep 26 17:56:54 2002

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