I suspect that the external isn't updated automatically for the committer in
this case is it?
I haven't used externals, but I'm willing to bet a fair amount of money
on it. The committer doesn't update any versioned files - neither those
being committed, because they _are_ the new version, no
> -Original Message-
> From: Stein Somers [mailto:ssom...@opnet.com]
> Sent: 24 February 2010 13:50
> To: users@subversion.apache.org
> Subject: Re: Modify files in start-commit
>
> On second thought, how about this: don't change the transaction, but
&g
On second thought, how about this: don't change the transaction, but
keep the VERSION file in a separate repository, that you reference
through svn:external. That way, you don't modify the contents of the
transaction - you just add a second transaction. Of course it's your
responsibility to tie
Hi
Not sure I really understand the problem, but how about creating a
tag(version) in post-commit?
/component/trunk -> /component/version/build
Cheers / Erik
On Wed, Feb 24, 2010 at 12:34 PM, Bailey, Darragh wrote:
>
> Is it possible to modify files in a start-commit hook and include them wit
On 24/02/2010 12:34, Bailey, Darragh wrote:
Is it possible to modify files in a start-commit hook and include them with a
commit?
As far as I know, you can't even tell which files are modified in the
start-commit hook.
You can tell in the pre-commit hook, but its template shouts
# *** N
Is it possible to modify files in a start-commit hook and include them with a
commit?
We have multiple components here in the same svn tree, and we'd like to bump a
release number on each one as commits occur. Rather than trying to add code to
check how many commits have been made to the area
