From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2977 invoked by alias); 26 Nov 2007 18:10:15 -0000 Received: (qmail 2864 invoked by uid 22791); 26 Nov 2007 18:10:13 -0000 X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 26 Nov 2007 18:10:07 +0000 Received: (qmail 29393 invoked from network); 26 Nov 2007 18:10:03 -0000 Received: from unknown (HELO digraph.polyomino.org.uk) (joseph@127.0.0.2) by mail.codesourcery.com with ESMTPA; 26 Nov 2007 18:10:03 -0000 Received: from jsm28 (helo=localhost) by digraph.polyomino.org.uk with local-esmtp (Exim 4.68) (envelope-from ) id 1IwiPC-0008Mb-04; Mon, 26 Nov 2007 18:10:02 +0000 Date: Mon, 26 Nov 2007 18:43:00 -0000 From: "Joseph S. Myers" To: Paolo Bonzini cc: GCC Development , Steven Bosscher Subject: Re: PR1634: Request for gcc-cvs-patches list In-Reply-To: <474B02C4.4040308@gnu.org> Message-ID: References: <571f6b510711260736v726d4564h2e1fabc4bb77ad03@mail.gmail.com> <474B02C4.4040308@gnu.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org X-SW-Source: 2007-11/txt/msg00675.txt.bz2 On Mon, 26 Nov 2007, Paolo Bonzini wrote: > On the other hand, if it is meant for human usage the file list is already a > clue to spot "wrong" commits. Then, an equivalent but more versatile feature > request would be to have patches visible online, with URLs like > http://gcc.gnu.org/viewcvs/?r1=119999r2=120000&view=patch (which would do a > "svn diff -x -u -r119999 -r120000"). Such URLs currently work with files but > not with directories. I don't know how fundamental a problem with ViewVC and > svn-python bindings this is. The primary function is for a human reading the list (where patches directly inline in the message are by far preferable to URLs). I believe the SVN log mailer supports mailing patches anyway. So you could get 90% of the benefit by having the SVN mailer run twice for each commit, once with the present configuration for gcc-cvs and once with a different configuration (including patches, 10MB message size limit (and a similarly large limit for the list itself), truncating rather than splitting anything larger) for gcc-cvs-patches. -- Joseph S. Myers joseph@codesourcery.com