From: Phil Muldoon <pmuldoon@redhat.com>
To: Andrew Cagney <cagney@redhat.com>
Cc: frysk@sourceware.org
Subject: Re: HACKING file
Date: Wed, 11 Jun 2008 01:33:00 -0000 [thread overview]
Message-ID: <484ED99B.6020900@redhat.com> (raw)
In-Reply-To: <484E8022.7030207@redhat.com>
Andrew Cagney wrote:
> We've the web pages GetInvolved and Build which are both included in
> the tar ball. A pointer to them from the top level would be useful.
Yeah that and a general ascii text description of where to go to find
out other info. I'll check something in tomorrow and people can
add/change it.
Regards
Phil
prev parent reply other threads:[~2008-06-10 19:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 13:23 Phil Muldoon
2008-06-10 16:16 ` Andrew Cagney
2008-06-11 1:33 ` Phil Muldoon [this message]
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=484ED99B.6020900@redhat.com \
--to=pmuldoon@redhat.com \
--cc=cagney@redhat.com \
--cc=frysk@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).