[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Empty commit

From: Andy Levy <andy.levy_at_gmail.com>
Date: 2007-06-13 16:15:31 CEST

On 6/13/07, Giulio Troccoli <Giulio.Troccoli@uk.linedata.com> wrote:
> No, I haven't. But the thing is that subversion does not say anything or
> return something else than 0. My problem is that if I have a commit in a
> script I would like to know whether it was an empty commit or not. Also,
> if a user does a commit the only way for them to know that something was
> actually committed is whether they have a new revision or not. However,
> we know users, and in case they don't have a new revision, I know
> already that they would complain that they didn't have any message to
> tell them they actually didn't commit anything.

If something actually commits, you'll get a string returned indicating
what revision was committed. If there's no commit, you'll get either a
blank response (exit 0 = no errors, nothing to do), or a string
indicating why the commit didn't happen (exit != 1, error occurred).

You can't have an "empty" commit as far as I know.

> You say it's the client. Does not mean that the server is not queried at
> all?

As far as I know, if the client doesn't see anything to commit (read:
it detects no changes in the WC), then it'll stop right there. Why
bother with a server trip at that point?

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jun 13 16:16:18 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.