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

Re: Empty commit behavior

From: Ryan Schmidt <subversion-2007b_at_ryandesign.com>
Date: Tue, 8 Jan 2008 16:46:42 -0600

On Jan 8, 2008, at 13:54, Joseph Armbruster wrote:

> I performed a search on the mailing list from subversion.tigris.org
> and was not able to find anything exactly like this. If this is not
> the appropriate place for this type of inquiry, my apologies in
> advance. Here's the scenario.
> Two developers are working out of a said repository within a sandbox
> say svn://repo/sandboxes/someone
> One developer (with an updated tree) attempted to perform a commit to
> a file: svn://repo/sandboxes/someone in which a .cs file was modified
> The commit processed, except the result was the following:
> If I perform a log on svn://repo there was a new revision number 1537,
> that contained the log message but no differences listed

No difference is listed when you run "svn diff -c 1537 svn://repo"
you mean?

What is shown for "svn log -v -r 1537 svn://repo"? Does it list
the .cs file's path and name below the log message?

> If I perform a log on svn://repo/sandboxes/someone, revision 1537 is
> nowhere visible.

Then r1537 apparently did not affect svn://repo/sandboxes/someone. It
apparently affected some other path of the repository. "svn log -v -r
1537 svn://repo" should tell you which one.

> I've never experienced this behavior before, so I wanted to open it up
> to the community. If you need any additional information, do not
> hesitate to contact me.
> The subversion version the repository was configured with:
> svn, version 1.4.5 (r25188)
> compiled Aug 22 2007, 20:49:04
> Client was using: TortoiseSVN 1.4.4, Build 9706

To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-01-08 23:47:37 CET

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.