> -----Original Message-----
> From: subversion@fluppet.demon.co.uk
> [mailto:subversion@fluppet.demon.co.uk]
> Sent: Wednesday, December 05, 2007 3:57 PM
> To: users@subversion.tigris.org
> Subject: Revision-global properties?
>
> A quick question about something which I suspect is against the
> Subversion philosophy -
You're trying to shoehorn change control information into a version
control tool.
In theory, you should have a defect/ticket/bug before you begin work.
Then when you check-in, you put the defect/ticket/bug number into the
log message for reference. (The commit hook would verify the a
defect/ticket/bug number exists in the comment and that the
defect/ticket/bug is valid, in a valid status, being applied to the
correct branch/trunk, etc..)
So, either store the information outside of subversion in a proper tool,
or, as you noticed, be prepared to implement some really ugly hacks that
will just cause pain and suffering to people and profits down the road.
> To summarise the process, since that's a bit wordy:
> 1) Commit code into svn/sw (get revision number)
> [Automated check-in mail goes out at this stage, sans images.]
> 2) Create svn/sw_checkin_images/[revision number]/ and add images
> 3) Commit the images (and get their URL on the svn web interface)
> 4) Update the log for the original check-in to point at them
Or commit all the reference material to the secondary repository first,
get the rev number, and then put the URL+Rev (and a short summary) into
the primary code repository log message and email. Since all the meaty
reference info is in a URL, when you finally do implement a real change
control system, you easily change the script to reference the change
control system's URL.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Dec 5 22:24:27 2007