public inbox for [email protected]
help / color / mirror / Atom feedFrom: David Fetter <[email protected]>
To: PostgreSQL Docs <[email protected]>
To: PostgreSQL Patches <[email protected]>
Subject: On patching without write access to CVS
Date: Sun, 13 May 2007 18:56:34 -0700
Message-ID: <[email protected]> (raw)
Folks,
Thanks to Andrew Dunstan for pointing me toward cvsutils. As not
everybody knows about them, here's a small patch which lets people
know at least in theory where they are.
Cheers,
D
--
David Fetter <[email protected]> http://fetter.org/
phone: +1 415 235 3778 AIM: dfetter666
Skype: davidfetter
Remember to vote!
Consider donating to PostgreSQL: http://www.postgresql.org/about/donate
Index: doc/FAQ_DEV
===================================================================
RCS file: /projects/cvsroot/pgsql/doc/FAQ_DEV,v
retrieving revision 1.135
diff -c -r1.135 FAQ_DEV
*** doc/FAQ_DEV 5 May 2007 14:33:55 -0000 1.135
--- doc/FAQ_DEV 14 May 2007 01:56:11 -0000
***************
*** 108,114 ****
work. Failure to do so might mean your patch is rejected. If your work
is being sponsored by a company, read this article for tips on being
more effective.
!
A web site is maintained for patches awaiting review,
http://momjian.postgresql.org/cgi-bin/pgpatches, and those that are
being kept for the next release,
--- 108,120 ----
work. Failure to do so might mean your patch is rejected. If your work
is being sponsored by a company, read this article for tips on being
more effective.
!
! To create patches which would otherwise require that you have write
! access to the CVS repository, for example ones that add or remove
! files, you can use cvsutils. The cvsutils toolchain is packaged
! for many operating systems and available in source form at
! http://www.red-bean.com/cvsutils/
!
A web site is maintained for patches awaiting review,
http://momjian.postgresql.org/cgi-bin/pgpatches, and those that are
being kept for the next release,
Index: doc/src/sgml/cvs.sgml
===================================================================
RCS file: /projects/cvsroot/pgsql/doc/src/sgml/cvs.sgml,v
retrieving revision 1.42
diff -c -r1.42 cvs.sgml
*** doc/src/sgml/cvs.sgml 27 Mar 2007 01:45:22 -0000 1.42
--- doc/src/sgml/cvs.sgml 14 May 2007 01:56:11 -0000
***************
*** 15,20 ****
--- 15,24 ----
<firstname>Thomas</firstname>
<surname>Lockhart</surname>
</author>
+ <author>
+ <firstname>David</firstname>
+ <surname>Fetter</surname>
+ </author>
</authorgroup>
<date>1999-05-20</date>
</appendixinfo>
***************
*** 150,155 ****
--- 154,166 ----
comes with <productname>CVS</productname>, or see the online
documentation at <ulink url="http://www.nongnu.org/cvs/"></ulink;.
</para>
+ <para>
+ For those things which <productname>CVS</productname> does not do
+ by itself, such as letting you create patches without write access,
+ you can use <productname>cvsutils</productname>, which is packaged
+ for many operating systems, or available in source form at <ulink
+ url="http://www.red-bean.com/cvsutils/"></ulink;.
+ </para>
</sect1>
<sect1 id="cvs-tree">
Attachments:
[text/plain] cvsutils.diff (2.5K, 2-cvsutils.diff)
download | inline diff:
Index: doc/FAQ_DEV
===================================================================
RCS file: /projects/cvsroot/pgsql/doc/FAQ_DEV,v
retrieving revision 1.135
diff -c -r1.135 FAQ_DEV
*** doc/FAQ_DEV 5 May 2007 14:33:55 -0000 1.135
--- doc/FAQ_DEV 14 May 2007 01:56:11 -0000
***************
*** 108,114 ****
work. Failure to do so might mean your patch is rejected. If your work
is being sponsored by a company, read this article for tips on being
more effective.
!
A web site is maintained for patches awaiting review,
http://momjian.postgresql.org/cgi-bin/pgpatches, and those that are
being kept for the next release,
--- 108,120 ----
work. Failure to do so might mean your patch is rejected. If your work
is being sponsored by a company, read this article for tips on being
more effective.
!
! To create patches which would otherwise require that you have write
! access to the CVS repository, for example ones that add or remove
! files, you can use cvsutils. The cvsutils toolchain is packaged
! for many operating systems and available in source form at
! http://www.red-bean.com/cvsutils/
!
A web site is maintained for patches awaiting review,
http://momjian.postgresql.org/cgi-bin/pgpatches, and those that are
being kept for the next release,
Index: doc/src/sgml/cvs.sgml
===================================================================
RCS file: /projects/cvsroot/pgsql/doc/src/sgml/cvs.sgml,v
retrieving revision 1.42
diff -c -r1.42 cvs.sgml
*** doc/src/sgml/cvs.sgml 27 Mar 2007 01:45:22 -0000 1.42
--- doc/src/sgml/cvs.sgml 14 May 2007 01:56:11 -0000
***************
*** 15,20 ****
--- 15,24 ----
<firstname>Thomas</firstname>
<surname>Lockhart</surname>
</author>
+ <author>
+ <firstname>David</firstname>
+ <surname>Fetter</surname>
+ </author>
</authorgroup>
<date>1999-05-20</date>
</appendixinfo>
***************
*** 150,155 ****
--- 154,166 ----
comes with <productname>CVS</productname>, or see the online
documentation at <ulink url="http://www.nongnu.org/cvs/"></ulink>.
</para>
+ <para>
+ For those things which <productname>CVS</productname> does not do
+ by itself, such as letting you create patches without write access,
+ you can use <productname>cvsutils</productname>, which is packaged
+ for many operating systems, or available in source form at <ulink
+ url="http://www.red-bean.com/cvsutils/"></ulink>.
+ </para>
</sect1>
<sect1 id="cvs-tree">
view thread (4+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: On patching without write access to CVS
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox