public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Tristan Gingold <gingold@adacore.com>
To: Binutils <binutils@sourceware.org>
Subject: Branch 2.21 created
Date: Fri, 05 Nov 2010 09:24:00 -0000	[thread overview]
Message-ID: <1C392579-E377-4045-A790-D6276B2FF31F@adacore.com> (raw)
In-Reply-To: <9CC4E1B5-1996-498E-80B7-0DDA3392B81F@adacore.com>

Hi,

I have just created the binutils-2_21 branch.

You can *backport* regression fixes, or documentation improvements.
For anything else or in case of doubt, do not hesitate to ask.

(Of course these rules will become more strict when the release will be created.  So do not hesitate to ask if you don't follow closely this mailing list).

Thanks,
Tristan.

  reply	other threads:[~2010-11-05  9:24 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-02 14:09 Release 2.21 - rough schedule Tristan Gingold
2010-09-07 16:38 ` Doug Kwan (關振德)
2010-09-18  2:59 ` Alan Modra
2010-09-20 15:48   ` Richard Earnshaw
2010-09-21  0:32     ` Alan Modra
2010-09-22 15:22       ` Tejas Belagod
2010-09-22 19:31       ` Richard Sandiford
2010-09-22 22:58         ` Maciej W. Rozycki
2010-09-23  7:17           ` Tristan Gingold
2010-09-23 12:19             ` Maciej W. Rozycki
2010-09-18  7:31 ` Matt Rice
2010-09-21  9:24 ` Mike Frysinger
2010-09-21  9:26   ` Tristan Gingold
2010-09-21  9:28     ` Kai Tietz
2010-09-21  9:31       ` Tristan Gingold
2010-09-21  9:44         ` Kai Tietz
2010-09-23  5:11 ` Dave Korn
2010-09-23  7:33   ` Tristan Gingold
2010-10-21 12:33 ` Release 2.21 - schedule Tristan Gingold
2010-11-03 14:12   ` Release 2.21 - branch on Friday ? Tristan Gingold
2010-11-04  2:40     ` Dave Korn
2010-11-04  8:11       ` Tristan Gingold
2010-11-05  9:24         ` Tristan Gingold [this message]
2010-12-08 19:38           ` Branch 2.21 created Andreas Schwab
2010-12-08 23:44             ` Alan Modra

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=1C392579-E377-4045-A790-D6276B2FF31F@adacore.com \
    --to=gingold@adacore.com \
    --cc=binutils@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).