A slight tangent, but I suggest using a modification history section in
the preamble/post-amble. Include the why (bug or requirement id), when,
who and a comment. (For who, we use a 3 letter acronym, the users
initials, for example. User ids create a security risk.) It also helps
to enforce some s
Ryan Schmidt wrote:
> Thomas 'PointedEars' Lahn wrote:
>> [...]
>> The problem was that this script missed to commit the first version of a
>> file, and I noticed that only after I had already worked with the
>> repository for quite a while. This is how I solved it (apparently,
>> somewhat):
>>
On Jun 2, 2010, at 10:20, Thomas 'PointedEars' Lahn wrote:
> I would like to insert an older version of a file that is already in a
> repository as a specific revision of that repository.
>
> I have searched in the SVN book, searched with Google with keywords like
> "subversion file history", a
Hello,
I would like to insert an older version of a file that is already in a
repository as a specific revision of that repository.
I have searched in the SVN book, searched with Google with keywords like
"subversion file history", asked in a local newsgroup, and scanned through
the messages h
