From: Josh Triplett <josh.trip@verizon.net>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com,
Christian Limpach <Christian.Limpach@cl.cam.ac.uk>
Subject: Re: [PATCH] Tidy up installation paths
Date: Fri, 09 Sep 2005 15:46:41 -0700 [thread overview]
Message-ID: <432210D1.7030106@verizon.net> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D32DD27@liverpoolst.ad.cl.cam.ac.uk>
[-- Attachment #1.1: Type: text/plain, Size: 621 bytes --]
Ian Pratt wrote:
>>The purpose of the cleanup is to avoid cluttering $PATH with
>>things that are executable in another way. Since xentop is
>>executable via xm top, this redundancy seemed unnecessary.
>>
>>It's up to Ian or Christian. I can go either way.
>
> I'd prefer 'xm top', but we do need to implement Josh's suggested
> fixups.
One other issue as well, by the way: with xentop as a separate command,
it can be documented through the use of a manpage (currently installed
into /usr/share/man/man1/xentop.1). However, with xentop only
executable via xm, it is not possible to "man xm top".
- Josh Triplett
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 251 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2005-09-09 22:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-08 23:10 [PATCH] Tidy up installation paths Ian Pratt
2005-09-09 22:46 ` Josh Triplett [this message]
2005-09-09 22:58 ` Christian Limpach
-- strict thread matches above, loose matches on Subject: below --
2005-09-08 20:48 Ian Pratt
2005-09-06 21:04 Anthony Liguori
2005-09-08 20:43 ` Josh Triplett
2005-09-08 22:59 ` Anthony Liguori
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=432210D1.7030106@verizon.net \
--to=josh.trip@verizon.net \
--cc=Christian.Limpach@cl.cam.ac.uk \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.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 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.