From: Christopher Faylor <cgf@redhat.com>
To: cygwin@cygwin.com
Subject: Re: Suggestion for Cygwin User's guide
Date: Mon, 03 Sep 2001 15:23:00 -0000 [thread overview]
Message-ID: <20010903182331.F3225@redhat.com> (raw)
In-Reply-To: <20010903182218.E3225@redhat.com>
On Mon, Sep 03, 2001 at 06:22:18PM -0400, Christopher Faylor wrote:
>On Tue, Sep 04, 2001 at 12:12:42AM +0200, Andreas Eibach wrote:
>>
>>> I don't think that the section should be duplicated but I do think that
>>> the setup part should have a link to the detailed CYGWIN description.
>>>
>>> I'd appreciate it if you could provide a patch to do this, in fact.
>>
>>No problem. :-)
>>OK, I attached a draft where you can see what I had in mind.
>>(_moved_, not _copied_, as you said, "you don't want it duplicate". It is
>>not duplicate now. :-)).
>>
>>Andreas
>>
>>P.S. Actually it would be better to have the SGML (or sorta) source handy
>>here, because editing the HTML reveals that it's generated by some
>>conversion tool (sgml to html or similar). Besides, I don't think the
>>maintainers like too see me hack around here like this, but what the
>>heck...:)
>
>Um, yeah. Any patches you send will have to be against the html source.
^^^^
sgml
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2001-09-03 15:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-03 14:25 Andreas Eibach
2001-09-03 14:34 ` Christopher Faylor
2001-09-03 14:39 ` Andreas Eibach
2001-09-03 14:48 ` Christopher Faylor
2001-09-03 14:54 ` Andreas Eibach
2001-09-03 14:59 ` Andreas Eibach
2001-09-03 15:02 ` Andreas Eibach
2001-09-03 15:22 ` Christopher Faylor
2001-09-03 15:23 ` Christopher Faylor [this message]
2001-09-03 15:38 ` Andreas Eibach
2001-09-05 9:31 ` Christopher Faylor
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=20010903182331.F3225@redhat.com \
--to=cgf@redhat.com \
--cc=cygwin@cygwin.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).