public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mordechai Ovits <movits@ovits.net>
To: "Mohammad A. Haque" <mhaque@haque.net>
Cc: Rick Hohensee <humbubba@smarty.smart.net>, linux-kernel@vger.kernel.org
Subject: Reason (was: Re: dropcopyright script)
Date: Wed, 14 Feb 2001 09:33:36 -0500	[thread overview]
Message-ID: <20010214093336.A8748@ovits.net> (raw)
In-Reply-To: <200102140647.BAA24740@smarty.smart.net> <3A8A86ED.F8397F69@haque.net>
In-Reply-To: <3A8A86ED.F8397F69@haque.net>; from mhaque@haque.net on Wed, Feb 14, 2001 at 08:23:57AM -0500

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.

Mordy

On Wed, Feb 14, 2001 at 08:23:57AM -0500, Mohammad A. Haque wrote:
> What prompted this? People are going to want copyright notices in a
> prominent place. Namely at the beginning of the code along with whatever
> instructions and cruft.
> 
> Rick Hohensee wrote:
> > 
> > .......................................................................
> > ## drop copyright notices to the bottoms of C files in current dir and
> > #     subs.
> > # /*
> > #  CopYriGHt Guess Who          2001            All reserves righted.
> > # */
> > 
> > grep -ilr "copyright" . > tempdropcopyrights
> > 
> > for f in `cat tempdropcopyrights`
> > do
> > ed $f <<HEREDOC
> > /[Cc][oO][pP][yY][rR][iI]/
> > ?\/\*?
> > .,/\*\//m$
> > wq
> > HEREDOC
> > done
> > ........................................................................
> > 
> 
> -- 
> 
> =====================================================================
> Mohammad A. Haque                              http://www.haque.net/ 
>                                                mhaque@haque.net
> 
>   "Alcohol and calculus don't mix.             Project Lead
>    Don't drink and derive." --Unknown          http://wm.themes.org/
>                                                batmanppc@themes.org
> =====================================================================
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 

  reply	other threads:[~2001-02-14 14:33 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   ` Mordechai Ovits [this message]
2001-02-14 14:34     ` Reason (was: Re: dropcopyright script) Yoann Vandoorselaere
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=20010214093336.A8748@ovits.net \
    --to=movits@ovits.net \
    --cc=humbubba@smarty.smart.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhaque@haque.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox