From: Ben Elliston <bje@redhat.com>
To: Hans-Peter Nilsson <hans-peter.nilsson@axis.com>
Cc: cgen@sources.redhat.com
Subject: Re: More doc patches: call toplevel directory toplevel; *.cpu files are in cpu/
Date: Mon, 28 Jan 2002 12:14:00 -0000 [thread overview]
Message-ID: <15445.45347.499532.250570@scooby.brisbane.redhat.com> (raw)
In-Reply-To: <200201281912.UAA09786@ignucius.axis.se>
>>>>> "Hans-Peter" == Hans-Peter Nilsson <hans-peter.nilsson@axis.com> writes:
Hans-Peter> It seems docs weren't updated after *.cpu files (I guess) moved
Hans-Peter> to cpu/ at the beginning of time. I think most people outside
Hans-Peter> Red Hat would be helped if the top-level directory is called
Hans-Peter> "toplevel" rather than "devo" without further explanation.
Hans-Peter> Ok to commit?
Yes, please do.
Ben
prev parent reply other threads:[~2002-01-28 20:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-28 11:12 Hans-Peter Nilsson
2002-01-28 12:14 ` Ben Elliston [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=15445.45347.499532.250570@scooby.brisbane.redhat.com \
--to=bje@redhat.com \
--cc=cgen@sources.redhat.com \
--cc=hans-peter.nilsson@axis.com \
/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).