All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: [RFC] Move gcc 4.4.3 recipes in favour of 4.4.4
Date: Mon, 10 May 2010 16:27:20 -0700	[thread overview]
Message-ID: <20100510232720.GA13708@gmail.com> (raw)

Hi

I would like to propose to move gcc 4.4.3 recipes to gcc 4.4.4, 
there are no additional patches that we need and 4.4.4 is superset
of bugfixes. I want to avoid adding additional recipes if we could.
4.4.3 is not so widely used in distributions unlike 4.4.2

I can also just add 4.4.4 and leave 4.4.3 as it is if someone wants
to keep using 4.4.3

Please cast your concerns

Thanks
-Khem



             reply	other threads:[~2010-05-10 23:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-10 23:27 Khem Raj [this message]
2010-05-11  4:37 ` [RFC] Move gcc 4.4.3 recipes in favour of 4.4.4 Martin Jansa
2010-05-11  5:28   ` Khem Raj
2010-05-11  8:39 ` Roman I Khimov
2010-05-12  9:39   ` Martin Jansa
2010-05-12  9:44     ` Michael 'Mickey' Lauer
2010-05-12 17:49       ` [RFC] Move sane-toolchain defaults for gcc binutils and eglibc Khem Raj
2010-05-12 21:28         ` Martin Jansa
2010-05-12 11:14     ` [RFC] Move gcc 4.4.3 recipes in favour of 4.4.4 Roman I Khimov

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=20100510232720.GA13708@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=openembedded-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.