This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Commit-acks
- To: Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>
- Subject: Re: Commit-acks
- From: Hans-Peter Nilsson <hp at bitrange dot com>
- Date: Fri, 24 Mar 2000 18:15:28 -0500 (EST)
- cc: gcc-patches at gcc dot gnu dot org
On Fri, 24 Mar 2000, Gerald Pfeifer wrote:
> On Thu, 16 Mar 2000, Hans-Peter Nilsson wrote:
> > BTW, is it really of value that I (and others) ack like this when
> > committing after approval? If not, I'll try to stop. If it is, someone
> > (perhaps I) could add a blurb to cvswrite.html with a reason.
>
> Please! :-)
Considering RTH:s and Jeff:s answers, that would be adding a blurb why
*not* to ack-when-committing, right? Like this?
Ok to commit?
Index: cvswrite.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/cvswrite.html,v
retrieving revision 1.20
diff -p -c -r1.20 cvswrite.html
*** cvswrite.html 2000/02/01 22:22:39 1.20
--- cvswrite.html 2000/03/24 23:11:19
*************** the appropriate policies.
*** 124,129 ****
--- 124,134 ----
pages, comments and similar stuff need not be approved. Just check in the
fix. We don't want to get overly anal about checkin policies.
+ <p>When you have checked in a patch exactly as it has been approved, you
+ do not no need to tell that to people -- including the approver. People
+ interested in when a particular patch is committed can check CVS or the <a
+ href="http://gcc.gnu.org/ml/gcc-cvs/"gcc-cvs</a> list.
+
<hr>
<a name="checkin"><h2>Checking in a change</h2></a>
brgds, H-P