One-time keyword substitution

for Rev. $RevOnce$ : DROP * FROM FOO; On commit, the file would change to Changes for Rev. 123: CREATE TABLE FOO; Changes for Rev. 124 : DROP * FROM FOO; Thus, the next commiter could use a new $RevOnce$ line. Is this possible at all? Sincerely, Philipp Leusmann -- Mit freundlichen Grüßen

Re: One-time keyword substitution

the deployer. Regards, Philipp Am 10.01.2011 16:15, schrieb Thorsten Schöning: Guten Tag Philipp Leusmann, am Montag, 10. Januar 2011 um 15:52 schrieben Sie: On commit, the file would change to Changes for Rev. 123: CREATE TABLE FOO; Changes for Rev. 124 : DROP * FROM FOO; Should this

merging strategy

Hi all, we are currently rethinking our svn branching strategy and one question came up. To explain what we are planning to do: We are going to use a release-branching, with adding new features to /trunk . At some point in time, we will create a ReleaseCandidate-branch from the trunk to /branc

Re: merging strategy

Thank for you hint, Bob, but I have doubts this way a merging works out for us, since we are working in a small team without "voting" each task. So, I have the fear, that changesets committed to trunk contain unrelated changes, which by accident make it into the branch. So, it would be nice to

Re: merging strategy

Am 17.02.2010 um 16:46 schrieb Rob van Oostrum: > On Wed, Feb 17, 2010 at 9:09 AM, Philipp Leusmann > wrote: > Thank for you hint, Bob, but I have doubts this way a merging works out for > us, since we are working in a small team without "voting" each task. So, I

Re: Check Client Version in hook

Great, information if mergeinfo is available if all we need to do. (We want to make sure only mergeinfo-supporting clients are allowed, as proposed in Maybe the way to do so (as shown in