From: Brian Friday <bfriday@lasierra.edu>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] gentoo text editors
Date: Wed, 10 Sep 2003 19:25:16 -0700 [thread overview]
Message-ID: <20030911020247.3705C94B99@mail.lasierra.edu> (raw)
In-Reply-To: <20030911014556.4104A94B94@mail.lasierra.edu>
Holy never finished the thought batman! Teaches me to spell
check before I finish...
---
Of course this only works in situations where a block has
been identified by developers but perhaps (again thinking
way ahead) doing a scan after the package has been imaged
(ie /var/tmp/portage/pkgname/image) but before it is
merged. This scan would check to make sure we won't be
overwriting an application/file with this new ebuild that
isn't an upgrade or downgrade of the package being built.
---
the full 2cents
- Brian
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-09-11 2:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-10 8:38 [gentoo-dev] gentoo text editors Matthew Kennedy
2003-09-10 9:12 ` Seemant Kulleen
2003-09-11 1:07 ` Matthew Kennedy
2003-09-11 2:08 ` Brian Friday
2003-09-11 2:25 ` Brian Friday [this message]
2003-09-11 3:54 ` Marius Mauch
2003-09-11 8:44 ` Matthew Kennedy
2003-09-11 4:13 ` C. Brewer
2003-09-11 7:54 ` donnie berkholz
2003-09-11 18:06 ` C. Brewer
2003-09-11 8:39 ` Matthew Kennedy
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=20030911020247.3705C94B99@mail.lasierra.edu \
--to=bfriday@lasierra.edu \
--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