From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: [commit/branch] Version set to 6.7.90
Date: Fri, 14 Mar 2008 21:17:00 -0000 [thread overview]
Message-ID: <20080314211725.GL31663@caradoc.them.org> (raw)
In-Reply-To: <20080314194437.GL3738@adacore.com>
On Fri, Mar 14, 2008 at 12:44:37PM -0700, Joel Brobecker wrote:
> All in all, I'm thinking that we should make it a policy of creating
> the pre-release immediately. The only case where this would provide
> no benefit is when we know a major piece is missing, but in this case
> the branch shouldn't have been cut in the first place, no?
Makes sense to me.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-03-14 21:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-13 17:52 Joel Brobecker
2008-03-14 10:21 ` Andreas Schwab
2008-03-14 17:29 ` Joel Brobecker
2008-03-14 17:58 ` Daniel Jacobowitz
2008-03-14 19:45 ` Joel Brobecker
2008-03-14 21:17 ` Daniel Jacobowitz [this message]
2008-03-14 18:06 ` Andreas Schwab
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=20080314211725.GL31663@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@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