Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
To: gdb-patches@sources.redhat.com
Subject: Re: New branch [was Re: RFC: MI output during program execution]
Date: Sat, 13 May 2006 02:28:00 -0000	[thread overview]
Message-ID: <17510.34460.791254.936961@kahikatea.snap.net.nz> (raw)
In-Reply-To: <20060512124331.GA3460@nevyn.them.org>

[-- Attachment #1: message body and .signature --]
[-- Type: text/plain, Size: 1110 bytes --]

                                      ref no: 6.4.50.20060512-nickrob-async

Daniel Jacobowitz writes:
> On Fri, May 12, 2006 at 08:36:44PM +1200, Nick Roberts wrote:
 > > Actually thats quite a lot of data and probably not of general interest.
 > > Shall I just post the ChangeLog?
 > 
 > I suppose; I can always grab the branch and diff it myself.

I attach a compressed diff as its not as big as I had thought it would be.

 ...
 > > I can't get my head round mergepoints (what happens if someone elso commit
 > > after your tag but before your commit?) but I'll worry about that later.
 > 
 > The trick is that you do everything relative to the tags, including
 > merges and other tags - nothing relative to HEAD.
 > 
 >   - Create new tag
 >   - Merge changes from last tag to new tag to branch.

Perhaps I'm confusing things a bit.  Maybe mergepoints are just for merging
HEAD to branch.  Is any tagging needed when the branch gets merged to HEAD?
(possibly a bit hypothetical as I realise I may never get that far).


-- 
Nick                                           http://www.inet.net.nz/~nickrob



[-- Attachment #2: Changes for 6.4.50.20060512-nickrob-async --]
[-- Type: application/octet-stream, Size: 36487 bytes --]

       reply	other threads:[~2006-05-13  1:46 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 [this message]
2006-05-13  8:03             ` Daniel Jacobowitz
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=17510.34460.791254.936961@kahikatea.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=gdb-patches@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