This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: How to manage multiple patches
- From: Daniel Jacobowitz <drow at false dot org>
- To: Kris Warkentin <kewarken at qnx dot com>
- Cc: gdb at sources dot redhat dot com
- Date: Wed, 8 Dec 2004 16:30:04 -0500
- Subject: Re: How to manage multiple patches
- References: <41B771DC.2040701@qnx.com>
On Wed, Dec 08, 2004 at 04:27:56PM -0500, Kris Warkentin wrote:
> 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.
Usually that's what I do. Otherwise, take a look at "quilt" or
"patch-scripts".
Of course, every patch that you post or commit should be tested
independently, unless you say very clearly otherwise...
--
Daniel Jacobowitz