All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OpenEmbedded Development mailing list
	<openembedded-devel@lists.openembedded.org>
Subject: why qpealarmclockapplet-1.0.9/missing-files.tar.gz in OE repo?
Date: Sun, 17 Jan 2010 04:29:22 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.00.1001170426100.4163@localhost> (raw)


$ git log recipes/qpealarmclock/qpealarmclockapplet-1.0.9/missing-files.tar.gz
commit 709c4d66e0b107ca606941b988bad717c0b45d9b
Author: Denys Dmytriyenko <denis@denix.org>
Date:   Tue Mar 17 14:32:59 2009 -0400

    rename packages/ to recipes/ per earlier agreement

    See links below for more details:
    http://thread.gmane.org/gmane.comp.handhelds.openembedded/21326
    http://thread.gmane.org/gmane.comp.handhelds.openembedded/21816

    Signed-off-by: Denys Dmytriyenko <denis@denix.org>
    ... snip ...

it would seem that you can download "missing-files.tar.gz" from here:

http://downloads.openmoko.org/developer/build/openembedded/packages/qpealarmclock/qpealarmclockapplet-1.0.9/

rather than keeping it in the repo.

rday
--

========================================================================
Robert P. J. Day                               Waterloo, Ontario, CANADA

            Linux Consulting, Training and Kernel Pedantry.

Web page:                                          http://crashcourse.ca
Twitter:                                       http://twitter.com/rpjday
========================================================================



             reply	other threads:[~2010-01-17  9:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-17  9:29 Robert P. J. Day [this message]
2010-01-17 12:42 ` [OT] Git: show commits belonging to renamed/moved files (was: why qpealarmclockapplet-1.0.9/missing-files.tar.gz in OE repo?) Paul Menzel
2010-01-18  7:07 ` why qpealarmclockapplet-1.0.9/missing-files.tar.gz in OE repo? Denys Dmytriyenko

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=alpine.LFD.2.00.1001170426100.4163@localhost \
    --to=rpjday@crashcourse.ca \
    --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.