You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by tr...@clayst.com on 2004/11/30 16:06:28 UTC
Setting Properties on Commit
So I am checking to see if I can save actual filesystem timestamps on
every commit.
I have a wrapper script that will do this by doing the commit then
using svnlook to find out what changed, taking all the items with 'A'
or 'U' in the first column, and doing an svn propset to save the
timestamps for those files and directories as a property.
The problem is this property is set only in the WC and requires another
commit to go to the repository.
If I do it in a post-commit hook I will have the same issue as I do
with a wrapper script.
If I do it in a pre-commit hook I can't (as far as I can tell) use
svnlook to get the file list, as at that point the commit has not been
done.
Is there any way around this, or does it require two commits to assign
a property value to each committed file using svnlook?
Thanks,
--
Tom
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Setting Properties on Commit
Posted by tr...@clayst.com.
On 1 Dec 2004 Ph. Marek wrote:
> It seems to my that you're not aware of issue 1256
> (http://subversion.tigris.org/issues/show_bug.cgi?id=1256), with the patch
> accompanying it, which probably does exactly what you want :-)
On second thought ... the build process on Windows is so daunting that
I'll live without that patch! I could do it, but setting up Subversion
is taking a lot of time already and I can't justify more to set up a
full source build, get Python, install Perl 5.8, extract this and that,
etc. Not a complaint, there's no reason someone should be making it
easier. It just doesn't work for me right now.
--
Tom
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Setting Properties on Commit
Posted by kf...@collab.net.
trlists@clayst.com writes:
> Hmmm, I see text-time in the entries file, but that doesn't appear to
> be a property. Is the name match between that item and patch 1256 a
> coincidence, or deliberate?
I think it's a coincidence, though it's a natural choice since they're
the same concept. I can't seem to get at P.Marek's patch, so I can't
check this for sure.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Setting Properties on Commit
Posted by tr...@clayst.com.
Hmmm, I see text-time in the entries file, but that doesn't appear to
be a property. Is the name match between that item and patch 1256 a
coincidence, or deliberate?
--
Tom
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Setting Properties on Commit
Posted by tr...@clayst.com.
On 1 Dec 2004 Ph. Marek wrote:
> It seems to my that you're not aware of issue 1256
> (http://subversion.tigris.org/issues/show_bug.cgi?id=1256), with the
> patch accompanying it, which probably does exactly what you want :-)
You're right, it looks like it does. Thanks! Now all I have to do is
set up the environment to do a build of the standalone version of
Subversion on Windows ...
--
Tom
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Setting Properties on Commit
Posted by "Ph. Marek" <ph...@bmlv.gv.at>.
On Tuesday 30 November 2004 17:06, trlists@clayst.com wrote:
> So I am checking to see if I can save actual filesystem timestamps on
> every commit.
...
> Is there any way around this, or does it require two commits to assign
> a property value to each committed file using svnlook?
It seems to my that you're not aware of issue 1256
(http://subversion.tigris.org/issues/show_bug.cgi?id=1256), with the patch
accompanying it, which probably does exactly what you want :-)
Regards,
Phil
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Setting Properties on Commit
Posted by tr...@clayst.com.
On 30 Nov 2004 Bryan Donlan wrote:
> > Now, here's an oddity ... why is it that if I do an svn status from the
> > top-level directory that's under version control (corresponds to the
> > top level in the repository) then I get (amid all the '?'s):
> >
> > M live\html\test1.php
> > .....
> > but if I do it from the live\html subdir I get no output???
>
> Works for me (subversion 1.1.1). Post a transcript and your version of
> subversion, please.
Never mind, just send me something to wipe the egg off my face :-). I
had a batch file called "svn" in the lowest level directory that I had
forgotten -- I was using it when developing a wrapper script. The
system was finding that instead of the real executable -- but only in
that directory.
--
Tom
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Setting Properties on Commit
Posted by Bryan Donlan <bd...@gmail.com>.
On Tue, 30 Nov 2004 13:05:14 -0500, trlists@clayst.com
<tr...@clayst.com> wrote:
> On 30 Nov 2004 Patrick Smears wrote:
>
> > You could use 'svn status' to determine what *will* be committed, and then
> > set the properties on those files prior to the actual commit. Would that
> > work for you?
>
> Yes, of course. I missed that one. All I have to do is do propsets on
> anything with an M or A in the first column.
>
> Now, here's an oddity ... why is it that if I do an svn status from the
> top-level directory that's under version control (corresponds to the
> top level in the repository) then I get (amid all the '?'s):
>
> M live\html\test1.php
>
> for the file I changed as a test, and if I do it from the live subdir I
> get:
>
> M html\test1.php
>
> but if I do it from the live\html subdir I get no output??? The same
> is true for svn list -R. Neither one works at the lowest level. What
> am I missing here??
Works for me (subversion 1.1.1). Post a transcript and your version of
subversion, please.
--
bd
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Setting Properties on Commit
Posted by tr...@clayst.com.
On 30 Nov 2004 Patrick Smears wrote:
> You could use 'svn status' to determine what *will* be committed, and then
> set the properties on those files prior to the actual commit. Would that
> work for you?
Yes, of course. I missed that one. All I have to do is do propsets on
anything with an M or A in the first column.
Now, here's an oddity ... why is it that if I do an svn status from the
top-level directory that's under version control (corresponds to the
top level in the repository) then I get (amid all the '?'s):
M live\html\test1.php
for the file I changed as a test, and if I do it from the live subdir I
get:
M html\test1.php
but if I do it from the live\html subdir I get no output??? The same
is true for svn list -R. Neither one works at the lowest level. What
am I missing here??
--
Tom
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Setting Properties on Commit
Posted by Patrick Smears <pa...@ensoft.co.uk>.
On Tue, 30 Nov 2004 trlists@clayst.com wrote:
> So I am checking to see if I can save actual filesystem timestamps on
> every commit.
>
> I have a wrapper script that will do this by doing the commit then
> using svnlook to find out what changed, taking all the items with 'A'
> or 'U' in the first column, and doing an svn propset to save the
> timestamps for those files and directories as a property.
>
> The problem is this property is set only in the WC and requires another
> commit to go to the repository.
>
> If I do it in a post-commit hook I will have the same issue as I do
> with a wrapper script.
>
> If I do it in a pre-commit hook I can't (as far as I can tell) use
> svnlook to get the file list, as at that point the commit has not been
> done.
>
> Is there any way around this, or does it require two commits to assign
> a property value to each committed file using svnlook?
You could use 'svn status' to determine what *will* be committed, and then
set the properties on those files prior to the actual commit. Would that
work for you?
Patrick
--
The easy way to type accents in Windows: http://www.frkeys.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org