From: Daniel Jacobowitz <drow@false.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb-patches@sources.redhat.com
Subject: Re: New branch [was Re: RFC: MI output during program execution]
Date: Sat, 13 May 2006 08:03:00 -0000 [thread overview]
Message-ID: <20060513022851.GA24947@nevyn.them.org> (raw)
In-Reply-To: <17510.34460.791254.936961@kahikatea.snap.net.nz>
On Sun, May 14, 2006 at 01:23:40PM +1200, Nick Roberts wrote:
> Perhaps I'm confusing things a bit. Maybe mergepoints are just for merging
> HEAD to branch.
Right.
> Is any tagging needed when the branch gets merged to HEAD?
> (possibly a bit hypothetical as I realise I may never get that far).
Not really. Normally, you'll just take the diff from the last
mergepoint to the branch tip, and apply that to HEAD, and declare the
branch dead - or declare the branch dead somewhat before that as the
patch gets reviewed, depending how it works out.
All this is much easier in non-CVS...
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-05-13 2:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <17458.60694.135878.624750@farnswood.snap.net.nz>
[not found] ` <20060404220637.GA12064@nevyn.them.org>
[not found] ` <17486.36188.127822.347550@farnswood.snap.net.nz>
[not found] ` <20060504150414.GE32605@nevyn.them.org>
[not found] ` <17508.18716.564160.93092@farnswood.snap.net.nz>
[not found] ` <20060512124331.GA3460@nevyn.them.org>
2006-05-13 2:28 ` Nick Roberts
2006-05-13 8:03 ` Daniel Jacobowitz [this message]
2006-05-15 16:58 ` PAUL GILLIAM
2006-05-13 9:07 ` Eli Zaretskii
2006-05-13 9:21 ` Nick Roberts
2006-05-13 10:34 ` Eli Zaretskii
2006-05-13 10:59 ` Nick Roberts
2006-05-14 7:35 ` {PATCH] gdbint.texi " Nick Roberts
2006-05-14 19:45 ` Eli Zaretskii
2006-05-15 0:56 ` {PATCH] gdbint.texi Nick Roberts
2006-05-15 10:19 ` Eli Zaretskii
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=20060513022851.GA24947@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=nickrob@snap.net.nz \
/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