public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: insight@sourceware.org
Subject: Re: gdb/gdbtk not tagged with gdb_7_0-branch tag
Date: Sun, 21 Feb 2010 17:48:00 -0000	[thread overview]
Message-ID: <20100202140603.2ff3232c@redhat.com> (raw)
In-Reply-To: <4B68635E.6020906@redhat.com>

On Tue, 02 Feb 2010 09:39:42 -0800
Keith Seitz <keiths@redhat.com> wrote:

> So, yes, you may tag the sources. [Don't forget gdb/testsuite/gdb.gdbtk.]

I've created the branch tag, gdb_7_0-branch, in the following locations:

    gdb/gdbtk
    gdb/testsuite/gdb.gdbtk
    tcl
    tk
    itcl
    libgui

I did not create a (non-branch) gdb_7_0_branchpoint tag, though I can
still do this if desired.  I doubt that there will be enough changes
put onto the insight portion of the branch for anyone to care... 
Also, creation of the branchpoint tag for insight has been erratic
over the last several GDB releases.  If a branchpoint tag is created,
I recommend that it be given the name gdb_7_0-2009-09-16-branchpoint,
even though that date isn't quite accurate for the tagging that I
did.  (I used "-D 2009-09-18" to check out the sources that I tagged.
Insight often lags GDB on necessary fixes by a few days, so it seemed
prudent to use a slightly later date.)

I've done a test checkout of the insight sources using the gdb_7_0-branch
branch tag.  Insight builds and runs on my machine.  Looking at
Help->About GDB... shows the correct version number.  I've not done
any testing beyond making sure that the gui comes up when invoked.

Kevin

      reply	other threads:[~2010-02-02 21:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-02 17:39 Kevin Buettner
2010-02-02 21:06 ` Keith Seitz
2010-02-21 17:48   ` Kevin Buettner [this message]

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=20100202140603.2ff3232c@redhat.com \
    --to=kevinb@redhat.com \
    --cc=insight@sourceware.org \
    /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).