[ I believe this is a repost of a patch I sent a few weeks ago,
but I didn't receive a response or it got lost. ]
Would anyone have a problem if I added this section to the CVS
users' guide? It basically attempts to say that pserver or explicit
anonymous users aren't needed. I know that when I first tried to
commit to a SVN repository, I got thrown for a loop trying to figure
out how to login before I committed. (At the time, I didn't know
that svn commit would do that for me!)
I think that the people who might be looking for this info would
be CVS die-hards, so this seems the most logical place. And, I'm
sure that someone could word this far better than I can if they
wanted. -- justin
doc/user/svn_for_cvs_users/svn_for_cvs_users.texi: Add new section
on differences in committing between CVS and SVN.
Index: svn_for_cvs_users.texi
===================================================================
--- .svn/text-base/svn_for_cvs_users.texi.svn-base Wed Jan 2 23:20:10 2002
+++ svn_for_cvs_users.texi Wed Jan 2 23:53:18 2002
@@ -34,6 +34,7 @@
* Directory versioning::
* Conflicts::
* Binary files::
+* Committing::
* Branches and tags::
* Real docs::
@end menu
@@ -343,6 +344,24 @@
update, no real merge occurs. Instead, Subversion creates two files
side-by-side in your working copy; the one containing your local
modifications is renamed with an ".orig" extension.
+
+
+
+@node Committing
+@section Committing
+
+Unlike CVS, SVN can handle anonymous and authorized users in the same
+repository. There is no need for an explicit anonymous user or separate
+repositories. If the SVN server requests authorization when committing,
+the client should prompt for authorization (password).
+
+Also, the command-line client does not currently bring up an editor.
+Therefore, you must write the log entry @b{before} committing and
+pass the log file path when committing:
+
+@example
+svn commit -F <path to your new log entry>
+@end example
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:57 2006