From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: drow@false.org
Cc: gdb@sources.redhat.com
Subject: Re: Product branches in the GDB repository?
Date: Fri, 25 Mar 2005 19:56:00 -0000 [thread overview]
Message-ID: <200503251956.j2PJuGt7023386@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <20050325194819.GA23274@nevyn.them.org> (message from Daniel Jacobowitz on Fri, 25 Mar 2005 14:48:19 -0500)
Date: Fri, 25 Mar 2005 14:48:19 -0500
From: Daniel Jacobowitz <drow@false.org>
Anyone have preferences on where to document branches? We don't
currently do that in GDB. Easiest would be a file gdb/BRANCHES,
parallel to binutils/BRANCHES, or on the "current CVS" page of the
web site.
I think gdb/BRANCHES is an excellent idea, especially since that's
what the binutils folks already do.
Hmm, that raises the question where to list the tag if people want to
branch gdb+binutils...
Mark
next prev parent reply other threads:[~2005-03-25 19:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-22 0:20 Daniel Jacobowitz
2005-03-22 0:37 ` Stan Shebs
2005-03-22 1:21 ` Nick Roberts
2005-03-22 2:38 ` Daniel Jacobowitz
2005-03-22 19:43 ` Stan Shebs
2005-03-29 0:53 ` Bob Rossi
2005-03-29 1:25 ` Stan Shebs
2005-03-25 19:47 ` Daniel Jacobowitz
2005-03-25 19:56 ` Mark Kettenis [this message]
2005-03-25 20:54 ` 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=200503251956.j2PJuGt7023386@elgar.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=drow@false.org \
--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