public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
To: crossgcc@sourceware.org
Cc: Joachim Nilsson <jocke@vmlinux.org>
Subject: Re: croostool-ng: GCC 4.4.1 Working!
Date: Sat, 26 Sep 2009 20:20:00 -0000	[thread overview]
Message-ID: <200909262219.58158.yann.morin.1998@anciens.enib.fr> (raw)
In-Reply-To: <4ABE32FF.70600@vmlinux.org>

Joachim,
All,

On Saturday 26 September 2009 17:27:59 Joachim Nilsson wrote:
> On 09/06/2009 01:01 PM, Joachim Nilsson wrote:
> > Anyway, I used the latest head (correct hg terminology?) of crosstool-ng
> > and added the 4.4.1 GCC patches from buildroot:
> > http://git.buildroot.net/buildroot/tree/toolchain/gcc/4.4.1
> > That's about it.
> > How would I proceed in contributing these patches, inline attachments,
> > publish a Mercurial branch, or is it sufficient with the above pointer?
> OK, so I don't want to sit on these patches any longer.

Yes, sorry... I have been a bit lazy the past few days (weeks) wrt
crosstool-NG... It's been threee years now I'm working on it, and
I feel a little bit blasé.

I'm a bit reluctant at applying your patch: there are currently 25 patches
applied to gcc-4.4.0, and I find it odd that 4.4.1 only requires 5.
I will try to forward-port the gcc-4.4.0 patchset up to 4.4.1.

And to answer your question, the README has a quick step-by-step example
on how to submit patches. It boils down to using Mercurial's patchbomb
extension.

Thank you!

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +0/33 662376056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| --==< ^_^ >==-- `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
`------------------------------^-------^------------------^--------------------'



--
For unsubscribe information see http://sourceware.org/lists.html#faq

  reply	other threads:[~2009-09-26 20:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-06 11:01 Joachim Nilsson
2009-09-26 15:28 ` Joachim Nilsson
2009-09-26 20:20   ` Yann E. MORIN [this message]
2009-09-28 13:40     ` Joachim Nilsson
2009-09-28 17:30       ` Yann E. MORIN

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=200909262219.58158.yann.morin.1998@anciens.enib.fr \
    --to=yann.morin.1998@anciens.enib.fr \
    --cc=crossgcc@sourceware.org \
    --cc=jocke@vmlinux.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).