This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
other/1634: Request for gcc-cvs-patches list
- To: gcc-gnats at gcc dot gnu dot org
- Subject: other/1634: Request for gcc-cvs-patches list
- From: Joseph Myers <jsm28 at cam dot ac dot uk>
- Date: Fri, 12 Jan 2001 18:40:27 +0000
- Cc: jsm28 at cam dot ac dot uk
>Number: 1634
>Category: other
>Synopsis: Request for gcc-cvs-patches list
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: unassigned
>State: open
>Class: change-request
>Submitter-Id: net
>Arrival-Date: Fri Jan 12 10:46:01 PST 2001
>Closed-Date:
>Last-Modified:
>Originator: Joseph S. Myers
>Release: 2.97 20010112 (experimental)
>Organization:
none
>Environment:
System: Linux decomino 2.2.18 #1 Sun Jan 7 21:04:55 UTC 2001 i686 unknown
Architecture: i686
host: i686-pc-linux-gnu
build: i686-pc-linux-gnu
target: i686-pc-linux-gnu
configured with: ../gcc-cvs/configure --prefix=/opt/gcc/snapshot --disable-shared --enable-threads=posix --with-system-zlib
>Description:
Could we please have a gcc-cvs-patches list, with all patches
automatically sent to it exactly as they are committed to CVS?
>How-To-Repeat:
Observe bogus changes in a commit not covered by the ChangeLog entry
or commit message, that could be more quickly detected if an automatic
mailing of committed patches were available.
>Fix:
Adapt the machinery that creates the gcc-cvs messages to also create
gcc-cvs-patches ones. These should include proper diffs for added /
deleted files, and for files that diff counts as binary; I suggest
-uapN as suitable GNU diff options, with the patch getting gzipped and
uuencoded if it is very large or passes some tests indicating it might
get corrupted in mailing (contains control characters other than
newline / tab / form feed or very long lines).
>Release-Note:
>Audit-Trail:
>Unformatted: