Re: svn diff and gvimdiff

Bryan Yeung <bryeung@gmail.com> writes:
> Thanks very much: that is exactly what I was looking for.
>
> Can someone point me at some guidelines/procedures for producing
> patches for the documentation? I'd be happy to write up something
> about this.

In this case, I think we'd want at least a patch for the FAQ, and
maybe one for the book. Let's start with the FAQ:

   1. Grab the latest Subversion www/ area tree by
      'svn co http://svn.collab.net/repos/svn/trunk/www/ svn-www'

   2. cd svn-www

   3. edit project_faq.html

   4. 'svn diff' | tee mypatch.txt

   5. edit mypatch.txt, putting a log message at the top, as per the
      guidelines in http://svn.collab.net/repos/svn/trunk/HACKING.

A similar procedure applies to the book, which is located in

   http://svn.collab.net/repos/svn/trunk/doc/book/book/
   (no, that's not a typo)

I'm not sure where in the book something like this should go; use your
judgement.

The patches should be posted here, with "[PATCH]" in the subject line.
See http://subversion.tigris.org/mailing-list-guidelines.html#patches
for more information.

Thanks!,
-Karl

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Nov 24 21:13:39 2004