From: Eldad Zack <eldad@gentoo.org>
To: Robert Moss <robmoss@gentoo.org>
Cc: Gentoo-Dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Upcoming repoman check will fail on large files in the tree
Date: Thu, 26 Aug 2004 17:34:58 +0300 [thread overview]
Message-ID: <1093530897.20234.24.camel@localhost> (raw)
In-Reply-To: <412CCA32.7020205@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 589 bytes --]
On Wed, 2004-08-25 at 20:19, Robert Moss wrote:
> Last time there was a big file QA check of the tree, someone said that
> certain things (such as bootloaders) were exempt. As such, despite the
> fact that I don't quite understand why splash.xpm.gz is in the tree
> rather than on the mirrors, when I last committed a new grub I left it
> there in files/.
Well, in that case, I really think you should put it on the mirrors
instead.
There are exactly zero reasons why it should be in CVS.
--
Eldad Zack <eldad@gentoo.org>
Key/Fingerprint at pgp.mit.edu, ID 0x96EA0A93
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-08-26 14:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-29 9:52 [gentoo-dev] Upcoming repoman check will fail on large files in the tree Brian Harring
2004-07-29 14:15 ` Mike Frysinger
2004-07-29 19:53 ` Jason Rhinelander
2004-07-30 3:15 ` Georgi Georgiev
2004-07-30 3:20 ` Brian Harring
2004-07-30 3:22 ` Ciaran McCreesh
2004-07-30 4:07 ` Ciaran McCreesh
2004-07-30 7:00 ` Robin H. Johnson
2004-07-30 7:43 ` Ciaran McCreesh
2004-08-25 6:56 ` Tavis Ormandy
2004-08-25 14:40 ` Mike Frysinger
2004-08-25 17:19 ` Robert Moss
2004-08-26 14:34 ` Eldad Zack [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-25 13:08 Peter Cech
2004-08-25 15:31 ` Andrew Cooks
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=1093530897.20234.24.camel@localhost \
--to=eldad@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=robmoss@gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox