You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Giulio Troccoli <Gi...@uk.linedata.com> on 2008/06/16 08:59:15 UTC

List of committed files for automatic merging

I'm in the process of implementing a serialized locking system for some
of our files.

I have set the svn:needs-lock property on those files and changed the
pre-commit hook (just for safety measure).

We also have an automatic merging process and I need a simple way to get
the list of files changed under a specific revision. I know two ways to
do that:
1 - use svnlook changed, however this wants the repository path and I'd
like to keep that out of the script that does the merge
2 - use svn log, however the list of files is between lots of other
information and it's not that easy to parse it out.

Is there any other way you can think of? If not I would probably use
svnlook as parsing the information is almost trivial. I will get over
the fact that the repository path is in the script :-)

Thanks
Giulio

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org


Re: List of committed files for automatic merging

Posted by Erik Huelsmann <eh...@gmail.com>.
On 6/16/08, Giulio Troccoli <Gi...@uk.linedata.com> wrote:
> I'm in the process of implementing a serialized locking system for some
> of our files.
>
> I have set the svn:needs-lock property on those files and changed the
> pre-commit hook (just for safety measure).
>
> We also have an automatic merging process and I need a simple way to get
> the list of files changed under a specific revision. I know two ways to
> do that:
> 1 - use svnlook changed, however this wants the repository path and I'd
> like to keep that out of the script that does the merge
> 2 - use svn log, however the list of files is between lots of other
> information and it's not that easy to parse it out.

svn log --xml ?

> Is there any other way you can think of? If not I would probably use
> svnlook as parsing the information is almost trivial. I will get over
> the fact that the repository path is in the script :-)

HTH,

Erik.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org