You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Joseph Armbruster <jo...@gmail.com> on 2008/01/08 19:54:20 UTC

Empty commit behavior

Greetings,

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
If I perform a log on svn://repo/sandboxes/someone, revision 1537 is
nowhere visible.

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


Thank you in advance,
Joseph Armbruster

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

Re: Empty commit behavior

Posted by Joseph Armbruster <jo...@gmail.com>.
Ryan,

Here is the information you requested with anything confidential removed:

On Jan 8, 2008 5:46 PM, Ryan Schmidt <su...@ryandesign.com> wrote:
> 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?

Correct, as illustrated here:

C:\work>svn diff -c 1537 svn://hostname:3690/repo

C:\work>

>
> 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?

C:\work>svn log -v -r 1537 svn://hostname:3690/repo
------------------------------------------------------------------------
r1537 | username | 2008-01-08 14:29:40 -0500 (Tue, 08 Jan 2008) | 1 line

Fixed the... (message continued here)
------------------------------------------------------------------------

C:\work>

>
> > 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
>
>

Thank you for the swift response.  Let me know if any other
information would help.

Joseph Armbruster

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

Re: Empty commit behavior

Posted by Ryan Schmidt <su...@ryandesign.com>.
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@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org