From: Joshua Brindle <method@manicmethod.com>
To: Vikram Noel Ambrose <noel.ambrose@gmail.com>
Cc: Stephen Smalley <sds@tycho.nsa.gov>,
Daniel J Walsh <dwalsh@redhat.com>,
Manoj Srivastava <srivasta@debian.org>,
Caleb Case <ccase@tresys.com>, SE Linux <selinux@tycho.nsa.gov>
Subject: Re: [PATCH][origin/autotools] fix libtool_compat header error
Date: Thu, 04 Sep 2008 10:09:05 -0400 [thread overview]
Message-ID: <48BFEC01.3080603@manicmethod.com> (raw)
In-Reply-To: <48BF5551.5080702@gmail.com>
Vikram Noel Ambrose wrote:
> Joshua Brindle wrote:
>> Vikram Ambrose wrote:
<snip>
> Oh before i forget. It would be nice to add NEWS, README and AUTHORS
> files to each package folder, no mandatory, but would make life easier,
> as these files need to be generated before autoconf can be run, and it
> would be better to have meaningful content for these files then stubbing
> it out on the fly from the autogen.sh script. If there is no objection I
> will create a separate commit for these files.
>
I removed them from the previous patch because they were incomplete and may have been seen as offensive to some (eg., the AUTHORS file only had you and I listed). There are quite a few contributors to this code and I'm not even sure if I could collect them all. Steve might be able to though, since he has some sort of bionic brain.
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2008-09-04 14:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <48B6FD13.1000204@windriver.com>
2008-09-04 1:55 ` [PATCH][origin/autotools] fix libtool_compat header error Joshua Brindle
2008-09-04 3:26 ` Vikram Noel Ambrose
2008-09-04 14:09 ` Joshua Brindle [this message]
2008-09-04 14:18 ` Stephen Smalley
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=48BFEC01.3080603@manicmethod.com \
--to=method@manicmethod.com \
--cc=ccase@tresys.com \
--cc=dwalsh@redhat.com \
--cc=noel.ambrose@gmail.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
--cc=srivasta@debian.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 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.