From: Daniel Jacobowitz <drow@false.org>
To: gdb@sources.redhat.com
Subject: Product branches in the GDB repository?
Date: Tue, 22 Mar 2005 00:20:00 -0000 [thread overview]
Message-ID: <20050322002034.GA19385@nevyn.them.org> (raw)
We're already pretty flexible about creating branches for development. Does
anyone have an object to branches for non-FSF releases? I think it's a
logical extension of current practice.
CodeSourcery does regular releases of an ARM toolchain, and we're going to
have a bunch of as yet unsubmitted GDB patches in our next release. Nothing
deliberately unsubmitted, of course, but things which need additional
polishing or review or input before they're ready for HEAD. I would prefer
to maintain them in the main repository, simply because it's easier with CVS.
And that way the patches are easily available for any curious GDB
developers.
FWIW, we already do this for both gcc and binutils.
--
Daniel Jacobowitz
CodeSourcery, LLC
next reply other threads:[~2005-03-22 0:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-22 0:20 Daniel Jacobowitz [this message]
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
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=20050322002034.GA19385@nevyn.them.org \
--to=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