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

Re: Dropping Subversion

From: Andreas Schweigstill <andreas_at_schweigstill.de>
Date: Tue, 27 Jan 2009 18:28:10 +0100

Hello!

Petra Margaritoff schrieb:
> You are right, properties would be just the thing. To my knowledge though, properties are available only
> - either for ALL files of ONE revision (versioned properties)
> - or for ONE file in ALL revisions (unversioned properties)

No, the versioned properties are available for single files and
directories. If a property is set on a directory it only addresses
the directory itself but not the files in it.

Revision properties are not related to any file but to the revision
itself. The check-in comment is such a property.

> What I would need is a property I can set on a file basis and which is valid for only one revision, say
> foo.c rev. 44 - PEER_REVIEWED_OK
> foo.h rev. 42 - PEER_REVIEWED_NOK
> foo.h rev. 43 - PEER_REVIEWED_OK

This is absolutely the case for normal versioned properties.

There are also some use cases of QA for which revision properties
can be usefull. If you won't rely on the check-in comment and a
path created by a tagging/branching/releasing operation you could
set a revision property like my_company:yes_this_is_really_a_new_
software_release.

With best regards
Andreas Schweigstill

PS.: If you need some consultancy services for SCM or embedded
  systems stuff don't heasitate to contact me directly, since
  Reinfeld isn't too far away from Kiel. ;-)

-- 
Dipl.-Phys. Andreas Schweigstill
Schweigstill IT | Embedded Systems
Schauenburgerstraße 116, D-24118 Kiel, Germany
Phone: (+49) 431 5606-435, Fax: (+49) 431 5606-436
Mobile: (+49) 171 6921973, Web: http://www.schweigstill.de/
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1059641
Received on 2009-01-27 18:28:31 CET

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.