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

Re: Subversion not recording commit history

From: Garrett Rooney <rooneg_at_electricjellyfish.net>
Date: 2005-12-22 22:28:43 CET

On 12/22/05, JP Hindin <jplist@kiwigeek.com> wrote:
>
> Greetings folks;
> I'm a new Subversion user and am having a bit of difficulty, as Subversion
> is not remembering any of the commit messages.
>
> The repository is set up on a Debian box (running the Sarge stable
> subversion package), running under it's own user/group. All users on the
> system expected to talk to Subversion are in the same group as subversion,
> and the repository directory has been 'chown -R svn:svn /svn/' to get it
> all on the correct permissions.
>
> I have imported, checked out, made multiple commits, and exported to the
> dev server with nary a hiccup. The file versions exported are the latest
> in my working copy, verifying that svn is revisioning correctly and is
> spitting out the latest 'copy' of the files.
>
> Unfortunately 'svn log' shows nothing except the initial import, and 'svn
> diff' returns empty handed.
>
> A snippet:
>
> jphindin@pinhead:/working$ svn status
> M callsched
> jphindin@pinhead:/working$ svn ci -m "Test message"
> Sending callsched
> Transmitting file data .
> Committed revision 17.
> jphindin@pinhead:/working$ svn log
> ------------------------------------------------------------------------
> r5 | jphindin | 2005-12-19 10:00:46 -0600 (Mon, 19 Dec 2005) | 2 lines
>
> Initial import of documents into trunk
> ------------------------------------------------------------------------
>
> Now, perhaps I'm missing something, but if history logging was working, an
> 'svn log' should most certainly display the "Test message" commit message.
> I am unsure where to look. Since I am able to update the repository
> without problems, I can't understand where any permissions errors could
> be.

Run 'svn update' after your commit. The log command defaults to
operate on the current working directory if you don't give it any
targets, and that directory is still on a previous revision, before
your commit, so you start at that older revision and go back, missing
the commit you just made. If you update that directory it'll show you
your commit.

See the docs on mixed revision working copies for details on how and
why this is done this way.

-garrett

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Dec 25 09:30:55 2005

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