From: Kris Warkentin <kewarken@qnx.com>
To: gdb@sources.redhat.com
Subject: How to manage multiple patches
Date: Wed, 08 Dec 2004 21:25:00 -0000 [thread overview]
Message-ID: <41B771DC.2040701@qnx.com> (raw)
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
next reply other threads:[~2004-12-08 21:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-08 21:25 Kris Warkentin [this message]
2004-12-08 21:30 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41B771DC.2040701@qnx.com \
--to=kewarken@qnx.com \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).