From: "Jan Lübbe" <jluebbe@lasnet.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: please stop updating efl SRCDATE, it breaks builds
Date: Tue, 22 Jul 2008 21:10:41 +0200 [thread overview]
Message-ID: <1216753841.11524.16.camel@localhost> (raw)
In-Reply-To: <200807212346.44576.mickey@vanille-media.de>
On Mon, 2008-07-21 at 23:46 +0200, Michael 'Mickey' Lauer wrote:
> > Please think of all this when wanting to bump SRCDATE the next time.
>
> Uhm... in all earnest you want to request people to stop updating a software
> because of upstream source fetching problems? Sorry, this won't work.
>
> I understand your problem, but I would have expected a more constructive
> proposal than a recommendation to stop updating software in OE.
How about fetching the source from their git mirror
(http://staff.get-e.org/)?
--
Jan Lübbe <jluebbe@lasnet.de> http://sicherheitsschwankung.de
gpg-key 1024D/D8480F2E 2002-03-20
fingerprint 1B25 F91F 9E7B 5D4F 1282 02D6 8A83 8BE4 D848 0F2E
next prev parent reply other threads:[~2008-07-22 19:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-21 21:34 please stop updating efl SRCDATE, it breaks builds Koen Kooi
2008-07-21 21:46 ` Michael 'Mickey' Lauer
2008-07-22 19:10 ` Jan Lübbe [this message]
2008-07-22 22:11 ` Michael 'Mickey' Lauer
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=1216753841.11524.16.camel@localhost \
--to=jluebbe@lasnet.de \
--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.