From: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: Patching eglibc for AArch64
Date: Tue, 04 Dec 2012 11:54:49 +0100 [thread overview]
Message-ID: <50BDD679.5030106@linaro.org> (raw)
In-Reply-To: <1354618155.25268.46.camel@ted>
W dniu 04.12.2012 11:49, Richard Purdie pisze:
> The main thing worrying me about these now is the size of the patches.
> I'd prefer not to add them into the main repository since they then
> become part of history and increase the repo size. I'd really therefore
> like to host the patches somewhere and then point SRC_URI at them.
>
> Is that something linaro can do or should we find somewhere on the
> yoctoproject.org infrastructure?
We can host those patches. I sent this version for review as I do
development with local patchsets. Will prepare version with hosted patches.
next prev parent reply other threads:[~2012-12-04 11:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-29 11:19 Patching eglibc for AArch64 Marcin Juszkiewicz
2012-12-04 9:56 ` Marcin Juszkiewicz
2012-12-04 10:49 ` Richard Purdie
2012-12-04 10:54 ` Marcin Juszkiewicz [this message]
2012-12-10 17:20 ` [PATCH] eglibc: add AArch64 support Marcin Juszkiewicz
2012-12-04 10:53 ` Patching eglibc for AArch64 Phil Blundell
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=50BDD679.5030106@linaro.org \
--to=marcin.juszkiewicz@linaro.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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