From: Pete Gavin <pete@gentoo.org>
To: gentoo-dev@cvs.gentoo.org
Subject: [gentoo-dev] patcher
Date: Wed Feb 14 11:52:02 2001 [thread overview]
Message-ID: <20010214115149.A16402@cvs.gentoo.org> (raw)
Hi,
I was wondering, wouldn't it be better to keep patches that are
gzipped in the distfiles directory, since cvs doesn't really work well
w/ binary files? I mean, I figure the only patches that should even be
managed by cvs are ones we create ourselves, and under normal
circumstances, those wouldn't be terribly large, so they could go w/o
being gzipped. And since most people update their portage tree using
rsync -z, they would be compressed before being sent over the network,
so that shouldn't cost too much extra bandwidth.
Pete
next reply other threads:[~2001-02-14 18:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-14 11:52 Pete Gavin [this message]
2001-02-14 11:57 ` [gentoo-dev] patcher Achim Gottinger
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=20010214115149.A16402@cvs.gentoo.org \
--to=pete@gentoo.org \
--cc=gentoo-dev@cvs.gentoo.org \
--cc=gentoo-dev@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