From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18573 invoked by alias); 8 Dec 2004 21:25:19 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 18557 invoked from network); 8 Dec 2004 21:25:14 -0000 Received: from unknown (HELO hub.ott.qnx.com) (209.226.137.76) by sourceware.org with SMTP; 8 Dec 2004 21:25:14 -0000 Received: from smtp.ott.qnx.com (smtp.ott.qnx.com [10.0.2.158]) by hub.ott.qnx.com (8.9.3/8.9.3) with ESMTP id QAA28483 for ; Wed, 8 Dec 2004 16:46:09 -0500 Received: from [10.12.1.181] (dhcpa181 [10.12.1.181]) by smtp.ott.qnx.com (8.8.8/8.6.12) with ESMTP id QAA31438 for ; Wed, 8 Dec 2004 16:25:14 -0500 Message-ID: <41B771DC.2040701@qnx.com> Date: Wed, 08 Dec 2004 21:25:00 -0000 From: Kris Warkentin User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) MIME-Version: 1.0 To: gdb@sources.redhat.com Subject: How to manage multiple patches Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-12/txt/msg00061.txt.bz2 I'm seeking the wisdom of the experienced free software developers. When you have a patch in your sandbox waiting to be committed, what do you do to keep working and not get scrambled? I've been pondering various solutions whereby I keep a text diff and do some clever combination of patching and reverting to get back to a state where I can just cvs commit but it seems like it could be fairly error prone. Do people just keep multiple sandboxed? Inquiring minds want to know. Thanks Kris