All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Halstead <michael@yoctoproject.org>
To: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: Best way to update gnu-config?
Date: Wed, 03 Oct 2012 10:24:23 -0700	[thread overview]
Message-ID: <506C74C7.7090006@yoctoproject.org> (raw)
In-Reply-To: <506C50E4.9040104@linaro.org>

[-- Attachment #1: Type: text/plain, Size: 1588 bytes --]

On 10/03/2012 07:51 AM, Marcin Juszkiewicz wrote:
> W dniu 18.09.2012 11:36, Richard Purdie pisze:
>> On Tue, 2012-09-18 at 11:29 +0200, Marcin Juszkiewicz wrote:
>>> W dniu 18.09.2012 11:08, Richard Purdie pisze:
>>>
>>>> The trouble was that upstream was in cvs. It was the only reason we
>>>> still had a dependency on cvs and we decided we wanted to kill it
>>>> which
>>>> isn't something I regret.
>>>
>>> There is git mirror hosted on gnu.org servers which can be used instead
>>> of cvs. OE-Core already has git-native.
>>
>> I remember the problem now, this was a circular dependency nightmare
>> (git-native depends on gnu-config-native and vice versa).
>>
>>>> Can you share a tarball of the updated (unpatched) upstream version
>>>> and
>>>> we'll put it into place alongside the other tarball on the server.
>>>
>>> http://people.linaro.org/~hrw/aarch64/gnu-config-20120814.tar.bz2
>>>
>>> 11:29 hrw@puchatek$ sha256sum gnu-config-20120814.tar.bz2
>>> 44f99a8e76f3e8e4fec0bb5ad4762f8e44366168554ce66cb85afbe2ed3efd8b
>>> gnu-config-20120814.tar.bz2
>>>
>>>> Michael (cc'd) should be able to do this. Once that is done you should
>>>> be able to send a patch as usual to update to the new version.
>>>
>>> Ok.
>>
>> Thanks, Michael should be able to take care of this later today (he's US
>> based).
>
> Michael: any update on it?
>
I'm sorry this is a case of bad e-mail filtering.

I've added this tarball at
http://downloads.yoctoproject.org/releases/gnu-config/ is that correct?

Michael Halstead
Yocto Project / Sys Admin




[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4516 bytes --]

  reply	other threads:[~2012-10-03 17:37 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-18  8:58 Best way to update gnu-config? Marcin Juszkiewicz
2012-09-18  9:00 ` [PATCH 1/2] ncurses: Update gnu-config files to version used by OE-Core Marcin Juszkiewicz
2012-09-18  9:00   ` [PATCH 2/2] db: " Marcin Juszkiewicz
2012-09-18 11:20     ` Burton, Ross
2012-09-18 11:43       ` Marcin Juszkiewicz
2012-09-18 10:40   ` [PATCH 1/2] ncurses: " Koen Kooi
2012-09-18 10:43     ` Marcin Juszkiewicz
2012-10-08 16:32       ` [PATCH 1/4] autotools.bbclass: update gnu-config files always Marcin Juszkiewicz
2012-10-09  4:38         ` Chris Larson
2012-10-09 20:01           ` [PATCH] " Marcin Juszkiewicz
2012-10-09 22:34             ` Richard Purdie
2012-10-10 10:55               ` Marcin Juszkiewicz
2012-09-18  9:08 ` Best way to update gnu-config? Richard Purdie
2012-09-18  9:29   ` Marcin Juszkiewicz
2012-09-18 10:36     ` Richard Purdie
2012-10-03 14:51       ` Marcin Juszkiewicz
2012-10-03 17:24         ` Michael Halstead [this message]
2012-10-03 17:25           ` Marcin Juszkiewicz
2012-10-08 16:24   ` [PATCH] gnu-config: update to 2012.08.14 to get support for AArch64 architecture Marcin Juszkiewicz

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=506C74C7.7090006@yoctoproject.org \
    --to=michael@yoctoproject.org \
    --cc=marcin.juszkiewicz@linaro.org \
    --cc=openembedded-core@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.