From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: RFC: Making it mandantory to have a checksums.ini entry
Date: Wed, 01 Oct 2008 09:06:15 +0200 [thread overview]
Message-ID: <gbv7h7$s6b$1@ger.gmane.org> (raw)
In-Reply-To: <200810010447.44667.zecke@selfish.org>
On 01-10-2008 04:47, Holger Freyther wrote:
> Hey,
>
> I constantly spend my day moving checksums from tmp/checksums.ini to the right
> place and I would like to make it mandatory to have a checksums.ini entry
> when adding new versions.
+1
>
> The spend time on copy and pasting a checksums.ini entry is really small and
> the value is very high.
I added a bunch checksums from my buildmachines and poky a while ago,
Marcins scripts make that really easy.
> Stuff like macports is forcing one to have checksums
> as well.
>
> The attached diff would force it.
How that that patch affect things fetched for a CVS_TARBALL_STASH, e.g.
git_foo.bar.tar.gz, since that one is unversioned and prone to change?
regards,
Koen
>
> comments appreciated
> z.
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
next prev parent reply other threads:[~2008-10-01 7:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-01 2:47 RFC: Making it mandantory to have a checksums.ini entry Holger Freyther
2008-10-01 2:58 ` Otavio Salvador
2008-10-01 7:06 ` Koen Kooi [this message]
2008-10-15 17:34 ` Holger Freyther
2008-10-15 17:51 ` Koen Kooi
2008-10-15 18:17 ` Marcin Juszkiewicz
2008-10-16 12:20 ` Sledz, Steffen
2008-10-16 12:39 ` Thomas Kunze
2008-10-16 12:44 ` Sledz, Steffen
2008-10-16 12:52 ` Thomas Kunze
2008-10-16 13:12 ` Sledz, Steffen
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='gbv7h7$s6b$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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.