All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ulf Samuelsson <openembedded-core@emagii.com>
To: openembedded-core@lists.openembedded.org
Subject: Possible stale tags in the download directory
Date: Wed, 07 Dec 2011 09:27:12 +0100	[thread overview]
Message-ID: <4EDF2360.7090402@emagii.com> (raw)


When I look at the "downloads" location I find a lot of files called.

"11_usagi_fix.patch.done"

but no  "11_usagi_fix.patch" file in the directory.

If this is a indication of that a patch has been downloaded,
what happens if you for some reason or other delete your
OE-core directory and keep the downloads directory.

When you start from fresh, all the tags are then stale.

(Deleting the "downloads" directory seems a bad idea)

I think that if there should be tags in the "downloads" directory,
they should only reflect things which are downloaded to the
"downloads" directory, and nothing else.

As for the tags in the directory, I think a better approach
is to download a file "tarball.tar.bz2" to a different filename first
I.E: "tarball.tar.bz2.in-progress"  and if the download completes
then move the file to "tarball.tar.bz2".
Should remove a lot of clutter from the "downloads" directory.

-- 
Best Regards
Ulf Samuelsson
eMagii




             reply	other threads:[~2011-12-07  8:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-07  8:27 Ulf Samuelsson [this message]
2011-12-07  9:16 ` Possible stale tags in the download directory Richard Purdie
2011-12-07 11:27   ` Ulf Samuelsson
2011-12-07 12:00     ` Koen Kooi
2011-12-07 14:30       ` Ulf Samuelsson
2011-12-07 14:37         ` Paul Eggleton
2011-12-07 15:00           ` Richard Purdie
2011-12-07 21:43             ` Khem Raj
2011-12-07 23:46               ` Ulf Samuelsson
2011-12-07 15:04     ` Richard Purdie

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=4EDF2360.7090402@emagii.com \
    --to=openembedded-core@emagii.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ulf@emagii.com \
    /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.