From: Mark Loeser <halcyon@whiterapid.com>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] Large files still in files/
Date: Sun, 06 Mar 2005 00:27:00 -0500 [thread overview]
Message-ID: <422A94A4.5080903@whiterapid.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0503052317010.10589@rutrow.coat.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Michael Sterrett -Mr. Bones.- wrote:
| I'd like to highlight the larger files still found in files/ directories:
There's also quite a large amount of binary files still in the tree. A
lot of them seem to be compressed patches. I'm not sure what should be
done with those, but I thought putting binary files into the tree was
discouraged unless absolutely necessary. Lots of 4k compressed patches
doesn't seem to be something absolutely necessary.
Mark Loeser
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCKpSjCRZPokWLroQRAmY2AKCJm4FeZ0SbeQDNe246TBHGoA5JegCeIBvj
P+Wh0vFQStmaishA4JpoErw=
=y+ER
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-03-06 5:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-06 4:19 [gentoo-dev] Large files still in files/ Michael Sterrett -Mr. Bones.-
2005-03-06 5:09 ` Robin H. Johnson
2005-03-08 10:15 ` Michele Noberasco
2005-03-08 13:26 ` Michele Noberasco
2005-03-06 5:27 ` Mark Loeser [this message]
[not found] ` <20050206.052901.4667@leftmind.net>
2005-03-06 18:10 ` Anthony de Boer
2005-03-06 20:25 ` Cory Visi
2005-03-07 16:57 ` Martin Schlemmer
2005-03-07 17:38 ` Malte S. Stretz
2005-03-07 17:54 ` Aron Griffis
2005-03-07 18:05 ` Ciaran McCreesh
2005-03-07 18:59 ` Chris Gianelloni
2005-03-07 18:52 ` Chris Gianelloni
2005-03-07 18:52 ` Lance Albertson
2005-03-07 19:15 ` Chris Gianelloni
2005-03-08 7:39 ` Martin Schlemmer
2005-03-07 15:34 ` Chris Gianelloni
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=422A94A4.5080903@whiterapid.com \
--to=halcyon@whiterapid.com \
--cc=gentoo-dev@gentoo.org \
--cc=gentoo-dev@robin.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