From: "Chad M. Huneycutt" <chad.huneycutt@acm.org>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] Script to make list of ebuilds without $Header$
Date: Wed Aug 15 09:15:02 2001 [thread overview]
Message-ID: <3B7A9126.80302@acm.org> (raw)
In-Reply-To: 01081516491803.00655@desktop.dan.net
Dan Armak wrote:
>Hi all,
>
>The following construct:
>
>#! /bin/sh
>for X in `find /usr/portage/ -name *.ebuild | sort`;
>do
>
> grep "\$Header" ${X} > /dev/null || echo ${X}
>
>done
>
Why don't we add two lines as the 4th and fifth line:
# $Header$
# ****** DELETE ANY BROKEN HEADER LINES, PLEASE *****
That way developers can clean up the headers as they modify an ebuild.
Chad
next prev parent reply other threads:[~2001-08-15 15:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-15 7:50 [gentoo-dev] Script to make list of ebuilds without $Header$ Dan Armak
2001-08-15 8:08 ` Dan Armak
2001-08-15 11:15 ` Dan Armak
2001-08-15 9:15 ` Chad M. Huneycutt [this message]
2001-08-15 11:30 ` Dan Armak
2001-08-15 12:44 ` Daniel Robbins
2001-08-15 12:56 ` Dan Armak
2001-08-30 6:12 ` Parag Mehta
-- strict thread matches above, loose matches on Subject: below --
2001-08-15 10:42 Peter Kadau
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=3B7A9126.80302@acm.org \
--to=chad.huneycutt@acm.org \
--cc=gentoo-dev@cvs.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