public inbox for cygwin-patches@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-patches@cygwin.com
Subject: Re: [PATCH] Cygwin: doc: drop mention of 32-bit installer
Date: Wed, 12 Jan 2022 20:25:06 +0100	[thread overview]
Message-ID: <Yd8rEsDBRyCL/2VE@calimero.vinschen.de> (raw)
In-Reply-To: <31607842-7ac3-44ee-8099-ae53de5d1ed0@dronecode.org.uk>

On Jan 12 19:17, Jon Turney wrote:
> On 12/01/2022 18:51, Corinna Vinschen wrote:
> > On Jan 12 15:52, Jon Turney wrote:
> > > Drop mention of 32-bit installer, since it's offically discouraged, and
> > > planned to be dropped soon.
> > > 
> > > Adjust various references to be something more generic, like 'the Cygwin
> > > Setup program' to accomodate this.
> > > ---
> > >   winsup/doc/faq-setup.xml | 12 +++----
> > >   winsup/doc/setup-net.xml | 74 ++++++++++++++++------------------------
> > >   2 files changed, 34 insertions(+), 52 deletions(-)
> > > [...]
> > >   <para>
> > > -On Windows Vista and later, <command>setup.exe</command> will check by
> > > +On Windows Vista and later, <command>setup</command> will check by
> >                ^^^^^
> > This will have to be changed for the master branch to mention W7
> > instead.  Vista is a dead stinkin' fish at that time.  That reminds me,
> > we have to do this throughout.  Do you want to or shall I?
> 
> Please go ahead.
> 
> In this particular case, the leading clause can simply be dropped, since
> "setup will check by default if it runs with administrative privileges ..."
> describes the behaviour on all supported Windows versions.

Yeah, makes sense.


Corinna

      reply	other threads:[~2022-01-12 19:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-12 15:52 Jon Turney
2022-01-12 18:51 ` Corinna Vinschen
2022-01-12 19:17   ` Jon Turney
2022-01-12 19:25     ` Corinna Vinschen [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=Yd8rEsDBRyCL/2VE@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin-patches@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).