From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
To: linux-mtd@lists.infradead.org
Subject: Re: [PATCH 1/2] --cvs-exclude for mkfs.jffs2
Date: Tue, 29 Nov 2005 10:18:18 -0500 [thread overview]
Message-ID: <v0sltfeb45.fsf@marajade.sandelman.ca> (raw)
In-Reply-To: 20051129100937.AF133353F54@atlas.denx.de
[-- Attachment #1: Type: text/plain, Size: 1399 bytes --]
>>>>> "Wolfgang" == Wolfgang Denk <wd@denx.de> writes:
Wolfgang> In message <v0mzjofaup.fsf@marajade.sandelman.ca> you wrote:
>> This adds an option to ignore CVS directories.
Wolfgang> This doesn't make sense to me. You can and should use "cvs
Wolfgang> export" to create the directory trees you want to package.
yes, one could do that. I chose not to.
It isn't like I forced this option to be on.
cvs export requires that I actually check my changes in before I can test
them, which causes a lot of needless churn.
It may also mean that developers in my team will check in debug statements
and forget to remove them.
Wolfgang> You use CVS, others use GIT, or Subversion, or ClearCase, or
Wolfgang> Monotone, or darcs, or ... - it would not be really practical
Wolfgang> to add special rules for everybody's favorite tool.
It would very much be practical to do this.
I'd rather have a more general --exclude.
Of course, you argue for removing equivalent options from rsync and other
things. Accept the patch or not.
--
] ON HUMILITY: to err is human. To moo, bovine. | firewalls [
] Michael Richardson, Xelerance Corporation, Ottawa, ON |net architect[
] mcr@xelerance.com http://www.sandelman.ottawa.on.ca/mcr/ |device driver[
] panic("Just another Debian GNU/Linux using, kernel hacking, security guy"); [
[-- Attachment #2: Type: application/pgp-signature, Size: 480 bytes --]
next prev parent reply other threads:[~2005-11-29 16:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-29 2:26 [PATCH 1/2] --cvs-exclude for mkfs.jffs2 Michael Richardson
2005-11-29 10:09 ` Wolfgang Denk
2005-11-29 10:41 ` Bernd Petrovitsch
2005-11-29 14:08 ` Jörn Engel
2005-11-29 15:18 ` Michael Richardson [this message]
2005-11-29 17:08 ` Josh Boyer
2005-11-29 17:12 ` Josh Boyer
2005-11-29 20:31 ` Michael Richardson
2005-11-29 20:46 ` Wolfgang Denk
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=v0sltfeb45.fsf@marajade.sandelman.ca \
--to=mcr@sandelman.ottawa.on.ca \
--cc=linux-mtd@lists.infradead.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