From: Dan Armak <danarmak@gentoo.org>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] Script to make list of ebuilds without $Header$
Date: Wed Aug 15 11:30:02 2001 [thread overview]
Message-ID: <01081520254802.24777@desktop.dan.net> (raw)
In-Reply-To: <3B7A9126.80302@acm.org>
> Why don't we add two lines as the 4th and fifth line:
> # $Header$
> # ****** DELETE ANY BROKEN HEADER LINES, PLEASE *****
That's easy enough to do. As long as we're sure that the 4th/5th line is
always the correct position. Can someone think of a problematic case? Do I
get the "go-ahead"?
--
Dan Armak
Gentoo Linux Developer, Desktop Team
Matan, Israel
next prev parent reply other threads:[~2001-08-15 17:29 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
2001-08-15 11:30 ` Dan Armak [this message]
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=01081520254802.24777@desktop.dan.net \
--to=danarmak@gentoo.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