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

Re: success with svn commit

From: Andy Levy <andy.levy_at_gmail.com>
Date: 2006-08-03 03:52:05 CEST

On 8/2/06, Roland Silver <rollos@kitcarson.net> wrote:
> Ryan,
> Gosh, Chapter one of the SVN book doesn't say anything about the user
> having to DO anything after issuing a commit command!
>
> Yes, TextWrangler opens a file called "svn-commit.2.tmp" with the
> following contents (not including the dashed lines):
> ---------------------
> --This line, and those below, will be ignored--
>
> M foo.c
> ---------------------
> I typed "fubar" at the top of the file, saved it, and closed the
> window -- and indeed the commit command finished with this three-line
> message:
> Sending foo.c
> Transmitting file data .
> Committed revision 2.
>
> What is the significance of the commit message that I type? Ie what
> does svn do with the "fubar"?

You really ought to read through more of the book before you "dive
in." Things will make much more sense then.

http://svnbook.red-bean.com/nightly/en/svn.tour.cycle.html#svn.tour.cycle.commit

The commit message is your mark in the repository explaining what and
why you're committing. The more informative and detailed you make it,
the more understandable the project history is. Subversion itself
doesn't care what your message is, but you and every other developer
will.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Aug 3 03:53:28 2006

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.