From: Peter Volkov <pva@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Usage of cp -i to prevent overwriting upstream files
Date: Wed, 21 Jan 2009 20:00:02 +0300 [thread overview]
Message-ID: <1232557202.7782.4.camel@localhost> (raw)
In-Reply-To: <4976205A.5030600@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 379 bytes --]
В Втр, 20/01/2009 в 21:04 +0200, Petteri Räty пишет:
> So do you think:
> a) cp -i is fine
No, interactivity is bad.
> b) this function should be added to eutils
> c) keep it restricted to java eclasses
I don't remember/know any other cases where this function can be useful.
So I think it's better to add it somewhere into java eclasses.
--
Peter.
[-- Attachment #2: Эта часть сообщения подписана цифровой подписью --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-01-21 17:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-20 19:04 [gentoo-dev] Usage of cp -i to prevent overwriting upstream files Petteri Räty
2009-01-20 19:24 ` Ferris McCormick
2009-01-20 19:37 ` Petteri Räty
2009-01-20 20:18 ` Ferris McCormick
2009-01-20 22:50 ` Jan Kundrát
2009-01-20 23:40 ` Ferris McCormick
2009-01-20 23:57 ` Jeremy Olexa
2009-01-21 17:00 ` Peter Volkov [this message]
2009-01-21 19:22 ` Santiago M. Mola
2009-01-31 8:13 ` Luca Barbato
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=1232557202.7782.4.camel@localhost \
--to=pva@gentoo.org \
--cc=gentoo-dev@lists.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