From: Yoann Vandoorselaere <yoann@mandrakesoft.com>
To: Mordechai Ovits <movits@ovits.net>
Cc: "Mohammad A. Haque" <mhaque@haque.net>,
Rick Hohensee <humbubba@smarty.smart.net>,
linux-kernel@vger.kernel.org
Subject: Re: Reason (was: Re: dropcopyright script)
Date: 14 Feb 2001 15:34:56 +0100 [thread overview]
Message-ID: <m366iduycv.fsf@localhost.localdomain> (raw)
In-Reply-To: <200102140647.BAA24740@smarty.smart.net> <3A8A86ED.F8397F69@haque.net> <20010214093336.A8748@ovits.net>
In-Reply-To: Mordechai Ovits's message of "Wed, 14 Feb 2001 09:33:36 -0500"
Mordechai Ovits <movits@ovits.net> writes:
> In newer file managers, the icon of a C file is a tiny image of the first
> few lines of text. If all files startt with a copyright, it's not much
> good. So running this on a local, personal, tree can be a good thing.
Modifying the file manager to take care of that would
be a proper solution I think...
--
-- Yoann http://www.mandrakesoft.com/~yoann/
C makes it easy to shoot yourself in the foot. C++ makes it harder,
but when you do, it blows away your whole leg. - Bjarne Stroustrup
next prev parent reply other threads:[~2001-02-14 14:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-14 6:47 dropcopyright script Rick Hohensee
2001-02-14 7:55 ` Russell King
2001-02-14 7:59 ` Jeff Garzik
2001-02-14 12:31 ` Richard Gooch
2001-02-14 12:32 ` Jeff Garzik
2001-02-14 8:09 ` Matthew Dharm
2001-02-14 12:34 ` Wichert Akkerman
2001-02-14 15:44 ` Jes Sorensen
2001-02-14 13:23 ` Mohammad A. Haque
2001-02-14 14:33 ` Reason (was: Re: dropcopyright script) Mordechai Ovits
2001-02-14 14:34 ` Yoann Vandoorselaere [this message]
2001-02-14 14:44 ` Mordechai Ovits
2001-02-14 18:36 ` Jamie Lokier
2001-02-14 15:00 ` Mohammad A. Haque
2001-02-14 15:03 ` Mordechai Ovits
2001-02-14 17:52 ` Gregory Maxwell
2001-02-14 18:09 ` Mordechai Ovits
2001-02-14 19:37 ` dropcopyright script Brett Person
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=m366iduycv.fsf@localhost.localdomain \
--to=yoann@mandrakesoft.com \
--cc=humbubba@smarty.smart.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mhaque@haque.net \
--cc=movits@ovits.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.