RE: Re: feature request: svn revision alias

First, can you find a way to send your posts in ASCII? My Outlook
insists on top-posting these unless I convert to text, which produces
the bizarre formatting seen in Andrew Reedick's reply (and I chose not
to do that this time around).
 
Second, you did not answer the question that comes with option (a): what
is the benefit? How would you name such a revision if you maintain
multiple projects in a single repository? Heck, even a single project
raises issues if you have more than one codeline. What does the alias
tell you? Can you give us a concrete example of how you would use the
alias in a specific context?
 

--
David
________________________________
	From: OS [mailto:os_at_portfoolio.com] 
	Sent: Wednesday, February 20, 2008 1:18 PM
	To: Reedick, Andrew
	Cc: users_at_subversion.tigris.org
	Subject: Re: feature request: svn revision alias
	
	
	It's (a) -- "a way to alias a REV number".
	As I said, call it revision aliasing or revision naming.
	
	svn alias/revalias/revname <rev> <name>
	(or svn alias/revalias/revname -r <rev> <name>, whatever is more
consistent)
	
	The effect would be that wherever I'm able to use a revision
number today
	I would be able to use a revision name/alias.
	
	
	Reedick, Andrew wrote: 
			From: OS [mailto:os_at_portfoolio.com] 
			Sent: Tuesday, February 19, 2008 2:11 PM
			To: Paul Koning
			Cc: users_at_subversion.tigris.org
			Subject: Re: feature request: svn revision alias
			
			Yes:
			
			Look, svn-people, all I was suggesting was a
practical, simple (I
			    
		thought) solution to a
		  
			common, simple problem. It's something that all
other SCMs offer and
			    
		it would appease
		  
			many people used to that type of procedure (I
think).
			
			As far I can see, all the machinery is already
there. The only thing
			    
		missing is the symbolic name.
		  
			Don't even call it tagging. svn promotes
tag-via-copy, fine. Call it
			    
		revision naming or aliasing,
		  
			whatever. And let the users use it as they see
fit. Or not. It would
			    
		be an option that wouldn't
		  
			bother anyone not using it.
			    
		
		
		*Grrrrrr*  You haven't sufficiently defined what you're
asking for.  Is
		it:
			a) a way to alias a REV number in the same
manner as HEAD, PREV,
		etc., or
			b) to implement a more traditional style of
tagging/labeling
		instead of using 'svn copy', or
			c) a way to 'tag' single files (or revisions) in
order to see
		what tag directories the version/revision is in, or
			d) something else?
			e) an easier way to query/search on revision
properties
		
		If it's 'a', then I ask what's the benefit?  A revision
refers to the
		entire repository, or to the actual file changes made in
that single
		revision.  A revision/alias simultaneously provides too
much and too
		little information to be useful in most cases.  A
revision alias could
		be useful for marking merge points, or promoted/tested
revisions, and
		would probably be less clumsy than using revision
properties.  Which
		implies that an easier way to query or search on
revision properties is
		what you're really after?  Ex:
			svn co -r prop:TESTED svn://some/where/foo.java
		Which actually sounds like a really good idea, IMO.
Let's call that
		option 'e'.
		
		
		*****
		
		The information transmitted is intended only for the
person or entity to which it is addressed and may contain confidential,
proprietary, and/or privileged material. Any review, retransmission,
dissemination or other use of, or taking of any action in reliance upon
this information by persons or entities other than the intended
recipient is prohibited. If you received this in error, please contact
the sender and delete the material from all computers. GA623
		
		
		
		
		
		  
*************************************************************************
This communication, including attachments, is
for the exclusive use of addressee and may contain proprietary,
confidential and/or privileged information.  If you are not the intended
recipient, any use, copying, disclosure, dissemination or distribution is
strictly prohibited.  If you are not the intended recipient, please notify
the sender immediately by return e-mail, delete this communication and
destroy all copies.
*************************************************************************