From: Kevin Buettner <kevinb@redhat.com>
To: insight@sourceware.org
Subject: Branch tag gdb_7_1-branch added for insight-specific sources
Date: Mon, 08 Mar 2010 21:54:00 -0000 [thread overview]
Message-ID: <20100223165914.447b1da2@redhat.com> (raw)
I've tagged the insight-specific sources with the branch tag,
gdb_7_1-branch. Specifically, I've tagged the following directories:
gdb/gdbtk
gdb/testsuite/gdb.gdbtk
tcl
tk
itcl
libgui
The rest of the GDB sources have already been tagged with
gdb_7_1-branch. Now that the insight-specific sources have also been
tagged, it is possible to check out insight using this the tag and
obtain a tree from which insight may be built. I've done a test
check out and build to verify that it can indeed be done. The version
number displayed by Help->About GDB... is correct. (I haven't done
any testing beyond this simple smoke test.)
I did not create a branch point tag, but can do so if desired. (Let
me know within the next few days...) If a branch point tag is desired,
it should be named gdb_7_1-2010-02-18-branchpoint in order to match
the rest of GDB. The date won't be quite right, but will be close
enough, and, IMO, it is more important that it match the tag used by
the rest of GDB.
Kevin
reply other threads:[~2010-02-23 23:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20100223165914.447b1da2@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).