From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3090 invoked by alias); 26 Oct 2007 18:51:10 -0000 Received: (qmail 3073 invoked by uid 22791); 26 Oct 2007 18:51:09 -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; Fri, 26 Oct 2007 18:51:05 +0000 Received: (qmail 12589 invoked from network); 26 Oct 2007 18:51:03 -0000 Received: from unknown (HELO localhost) (jimb@127.0.0.2) by mail.codesourcery.com with ESMTPA; 26 Oct 2007 18:51:03 -0000 To: Ulrich Weigand CC: gdb-patches@sourceware.org Subject: Managing long patch series From: Jim Blandy Date: Fri, 26 Oct 2007 18:56:00 -0000 Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2007-10/txt/msg00719.txt.bz2 Ulrich, I'm curious what techniques you use to manage these long strings of patches. Specifically, I was wondering: - I'm usually working from a fully-patched tree, and then breaking it up into digestible pieces for submission. If you are working this way as well, do you have a nice way to ensure the decomposed patch series remains equivalent to your fully-patched tree? - Often I find I need to revise an earlier patch in the series, but that chance may affect later patches. Do you have a nice way to handle this? Or is it all just "blood, sweat, and tears"? In the software world, that approach usually results in "mistakes", but you and your fellow IBM GDB hackers seem to do well. I've tried using quilt, but if one doesn't keep very careful track of what's going on things can get very tangled. The Emacs mode helped somewhat, but had other flaws, so I set it aside. I've been tempted to try using Mercurial for this.