I'm trying to find out how one can put branch documentation in the
branch itself. By branch documentation I mean information such as
- parent branch
- codeline policy
Such information has to be versioned within the branch, but is owned by
the branch and does not make sense in other branches. In particular, it
must not be merged back to the trunk, which has its own documentation.
How does one manage such information with Subversion ? I'd imagine such
custom information to be typically stored in one or several files, that
would have to be checked out in working copies and commited back to the
branch (so svn:ignore won't do), but ignored when merging (and maybe
also when creating branches / tags).
I'm currently using Subversion 1.2.3 and am rather new to SCM an
Subversion in particular. In my company we've got a few small products
developed in java, in a very strict component-oriented way (dependency
control). Our java developments are expected to grow and we can't go on
developing without a decent versioning tool... I've gone trough the svn
book, suclipse help, this user mailing list archives, but haven't found
an answer to the issue above.
Thanks for your help and advice.
Le present courriel, y compris les pieces jointes, s'adresse exclusivement a la (aux) personne(s) ou a la societe a laquelle (auxquelles) il est destine et peut comporter des informations confidentielles et/ou protegees par la loi. Toute divulgation, reproduction ou utilisation de ces informations est interdite et peut etre illegale. Si vous n'etes pas destinataire de ce courriel, merci de le detruire immediatement et d'en aviser l'expediteur.
This e-mail, including attachments, is intended for the person(s) or company named and may contain confidential and/or legally privileged information. Unauthorized disclosure, copying or use of this information may be unlawful and is prohibited. If you are not the intended recipient, please delete this message and notify the sender.
Received on Fri Dec 22 14:21:36 2006