Re: Subversion First-class Labels

I second (or is it third?) this motion.

Tags are pain to work with. They are simply branches which people
promise not to modify. There's also no easy way to prevent users from
corrupting them (except through a custom pre-commit hook).

What I'd really like is a way to use first class tags the same way we
use revisions. Being able to do things such as:

$ svn diff -rREL-1.0:REL-2.0

Or

$svn cp -rREL-1.2.3 file:///some/directory/file_at_REL-1.2.3
file:///some/other/directory/new-file

I'll accept the ability to have these first class tags as mere aliases
to revision numbers if that makes things simpler.

I like the way Perforce has two separate types of labels (as they call
them). Label type #1 is applying the label to individual revisions of
files much like CVS. Label type #2 is simply states a revision number,
and a range of files to include with that label. I really like label
type #2. It's faster, and there's less of a chance that you'll
accidently label the wrong revision.

--
David Weintraub
qazwart_at_gmail.com
On Mon, Oct 20, 2008 at 4:53 PM, Joe Bell <joe.bell_at_prodeasystems.com> wrote:
> I agree with Steve here- I'm familiar with cheap copies and arranging my
> repository into tags, branches, trunk, etc.  but I really am looking
> for more than just a "convention" (labels/tags are cheap copies) and
> something more concrete.
>
> One example I can think of is branching from a label and rebasing from a
> label.
> I'd like to label the trunk as say BUILD1, branch a feature branch off
> of
> that label specifically (svn copy -rBUILD1 http://blah/svn/trunk
> http://blah/svn/branches/feature)
> and then rebase periodically
>
> In the feature branch, svn merge -rBUILD2 .
>
> or something like that (I realize my label could be on something other
> than the trunk
> but hopefully I could put a trigger in place to stop that).
>
> Admittedly I am more familiar the Clearcase label concept which I value
> highly.
>
>
> ---
>
> With all due respect, cheap copies don't really provide the
> functionality of labels with the simplicity and speed that CVS,
> Clearcase, or Perforce can do.  This particular use-case isn't well
> supported in Subversion as of today.  One of the reasons for this
> being that it is a major pain to figure out the following:
>
> 1. Which "labels" include this particular version of a file?
> 2. What are the revisions included in a particular "label"?
>
> Yes, you can datamine this information using svn log, but it requires
> some work (especially #1).
>
> -steve
> -----Original Message-----
> From: Steven Bakke [mailto:steven.bakke_at_amd.com]
> Sent: Monday, October 20, 2008 1:40 PM
> To: Erik Huelsmann
> Cc: Joe Bell; users_at_subversion.tigris.org
> Subject: Re: Subversion First-class Labels
>
>
> On Oct 20, 2008, at 2:04 PM, Erik Huelsmann wrote:
>
>> On Mon, Oct 20, 2008 at 7:50 PM, Joe Bell
>> <joe.bell_at_prodeasystems.com> wrote:
>>> I was browsing the web looking for an answer to the question as to
>>> whether
>>> first-class labels were going to be a planned addition to
>>> Subversion, but
>>> the best I could come up with was a lengthy discussion on SVN DEV
>>> back in
>>> 2005.  I'm curious as to whether anyone knows where this proposal
>>> is or is
>>> headed?
>>
>> I don't think there's been a serious follow-up.
>>
>>>
>>> By first-class labels I mean labels analogous to Clearcase, you
>>> create a
>>> label and then apply it to multiple elements (files, directories),
>>> etc. to
>>> provide a mnemonic name for a given configuration of files.
>>
>> Subversion can do this with tags: a tag can consist of any combination
>> of files in the repository and locally modified files.
>>
>
> With all due respect, cheap copies don't really provide the
> functionality of labels with the simplicity and speed that CVS,
> Clearcase, or Perforce can do.  This particular use-case isn't well
> supported in Subversion as of today.  One of the reasons for this
> being that it is a major pain to figure out the following:
>
> 1. Which "labels" include this particular version of a file?
> 2. What are the revisions included in a particular "label"?
>
> Yes, you can datamine this information using svn log, but it requires
> some work (especially #1).
>
> -steve
>
>
>> HTH,
>>
>>
>> Erik.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
>> For additional commands, e-mail: users-help_at_subversion.tigris.org
>>
>>
>
>
>
>
>
> This message is confidential to Prodea Systems, Inc unless otherwise indicated
> or apparent from its nature. This message is directed to the intended recipient
> only, who may be readily determined by the sender of this message and its
> contents. If the reader of this message is not the intended recipient, or an
> employee or agent responsible for delivering this message to the intended
> recipient:(a)any dissemination or copying of this message is strictly
> prohibited; and(b)immediately notify the sender by return message and destroy
> any copies of this message in any form(electronic, paper or otherwise) that you
> have.The delivery of this message and its information is neither intended to be
> nor constitutes a disclosure or waiver of any trade secrets, intellectual
> property, attorney work product, or attorney-client communications. The
> authority of the individual sending this message to legally bind Prodea Systems
> is neither apparent nor implied,and must be independently verified.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
> For additional commands, e-mail: users-help_at_subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org