All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcin Juszkiewicz <openembedded@hrw.one.pl>
To: openembedded-devel@lists.openembedded.org
Subject: RFC: /removal.txt - list of metadata planned for removal
Date: Fri, 17 Nov 2006 00:42:28 +0100	[thread overview]
Message-ID: <200611170042.29062.openembedded@hrw.one.pl> (raw)


During this week I'm fetching sources for whole 'world' and noticed many 
unfetchable things. Because just dropping them from metadata is not best 
way I was thinking about creating file with informations which parts of 
metadata will be removed. File will be named 'removal.txt' and will 
reside in / of repository.

Proposed format:

Package Name:	plinciv
Removal Date:	2006-11-20
Maintainer:	none
Reason:		Unfetchable version from 2003 year.


What do you think about it?

-- 
JID: hrw-jabber.org
OpenEmbedded developer/consultant

               Don't personalize computers. They hate that.





             reply	other threads:[~2006-11-16 23:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-16 23:42 Marcin Juszkiewicz [this message]
2006-11-16 23:51 ` RFC: /removal.txt - list of metadata planned for removal Justin Patrin
2006-11-18  1:36 ` Paul Sokolovsky
2006-11-18  8:02   ` Koen Kooi

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=200611170042.29062.openembedded@hrw.one.pl \
    --to=openembedded@hrw.one.pl \
    --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.