Propertites on Revision (not files) (Was Defining branch life-cycles in subversion)

[pw...@mdtsoft.com]

On  8 Nov, Ben Collins-Sussman wrote:
> Garrett Rooney <ro...@electricjellyfish.net> writes:
> 
>> Greg Dickie wrote:
>> 
>> >Hi,
>> >
>> >  I'm trying to put a layer on top of subversion in order to enforce
>> > a development process with things like code reviews, automated
>> > merging, etc. I hace done this before with clearcase. I was thinking
>> > I could use unversioned properties on a branch URL to keep things
>> > like state information but I guess I didn't understand how
>> > properties were implemented.
>> 
>> why do you want to use unversioned properties?  is there anything
>> keeping you from using standard versioned properties?
> 
> And anyway, there *are* unversioned properties, but they only exist on
> the revision itself, i.e. they're attached to the tree as a whole.
> The only unversioned props we're using right now are "svn:date",
> "svn:author", and "svn:log".  But you're certainly free to attach any
> other unversioned props to trees.

How do you attach propertites (say mdt:eco for an Engineering Change
Order Number) to a revisions when you do the commit? 

The book and quick reference guide don't say as far as I can find.


> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org

-- 
It is MDT, Inc's policy to delete mail containing unsolicited file attachments.
Please be sure to contact the MDT staff member BEFORE sending an e-mail with
any file attachments; they will be able to arrange for the files to be received.

This email, and any files transmitted with it, is confidential and intended
solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error, please advise postmaster@mdtsoft.com
<ma...@mdtsoft.com>.

Philip W. Dalrymple III <pw...@mdtsoft.com>
MDT Software - The Change Management Company
+1 678 297 1001 Fax +1 678 297 1003


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: Propertites on Revision (not files) (Was Defining branch life-cycles in subversion)

[pw...@mdtsoft.com]

On  8 Nov, Ben Collins-Sussman wrote:
> pwd@mdtsoft.com writes:
> 
>> How do you attach propertites (say mdt:eco for an Engineering Change
>> Order Number) to a revisions when you do the commit? 
>> 
>> The book and quick reference guide don't say as far as I can find.
> 
> Oops, sorry, unversioned revision-props have always been part of the
> repository (e.g svn:log, svn:date, etc.), but only recently have
> clients been able to tweak them over the network.  We've not yet
> documented the feature anywhere put in 'svn help propset':
> 
>    svn propset -rN propname propval

So what I have to do is

1) make changes to code
2) do the propset thing above
3) svn commit

Humm I was thinging (and looking) at the commit command.... but I think
that a seperate command..... wait one. what about the following case.

BACKGROUND

 we have a thing called an eco (think of it as a bugzilla number) that
 an engineer MUST have to make any change to the code. 

NOW

I am working on say eco-10501 and eco-10515 and have changed /bar/foo/stuff.c
for 10515 and have change /bas/bas/main.c for 10501.

I have finished 10501 and will 

cd /bas/bas and do a svn commit  (ecos tend to be from one point in the tree
 down)

I will enter my comment (under CVS we have a template with the eco: and
 a script that rejects the commit if that is not correct) and commit

if I do the svn propset -rN eco 10501 and forget to do 
svn propset -rN eco 10515 before my next commit then I will have the incorect
eco in the commit that takes care of 10515.


I can of course wrap this in a script so that the engineer has to enter
the eco each time.
> 
> Also, the UI will be changing soon, so don't habituate just yet.  :-)
> 
>    
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org

-- 
It is MDT, Inc's policy to delete mail containing unsolicited file attachments.
Please be sure to contact the MDT staff member BEFORE sending an e-mail with
any file attachments; they will be able to arrange for the files to be received.

This email, and any files transmitted with it, is confidential and intended
solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error, please advise postmaster@mdtsoft.com
<ma...@mdtsoft.com>.

Philip W. Dalrymple III <pw...@mdtsoft.com>
MDT Software - The Change Management Company
+1 678 297 1001
Fax +1 678 297 1003




---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: Propertites on Revision (not files) (Was Defining branch life-cycles in subversion)

[Ben Collins-Sussman <su...@collab.net>]

pwd@mdtsoft.com writes:

> How do you attach propertites (say mdt:eco for an Engineering Change
> Order Number) to a revisions when you do the commit? 
> 
> The book and quick reference guide don't say as far as I can find.

Oops, sorry, unversioned revision-props have always been part of the
repository (e.g svn:log, svn:date, etc.), but only recently have
clients been able to tweak them over the network.  We've not yet
documented the feature anywhere put in 'svn help propset':

   svn propset -rN propname propval

Also, the UI will be changing soon, so don't habituate just yet.  :-)

   

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org