public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ralph Hempel <rhempel@bmts.com>
To: cygwin@cygwin.com
Subject: Re: setup.exe command line parameters
Date: Tue, 24 Jun 2008 00:40:00 -0000	[thread overview]
Message-ID: <48603D26.2020302@bmts.com> (raw)
In-Reply-To: <005a01c8d528$fa4197f0$2708a8c0@CAM.ARTIMI.COM>

Dave Korn wrote:

>   Well, it needs a little debugging first, but it shouldn't be tricky to
> bash into shape.

Sorry for taking so long, but here's what we have so far. The "newer"
patch referred to by Reini is against but the patch is against 2.590
which looks like it's a bout 2 point releases behind the current version
in the 1.7 tree for setup.

The current "released" version of setup is 2.573.2.2

So the question is, if I'm going to look at patching setup to accept
a list of packages on the command line, then which version should
we be merging the patches against?

Ralph

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

  reply	other threads:[~2008-06-24  0:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-20 19:54 Ralph Hempel
2008-06-20 21:53 ` cuicui
2008-06-21  0:44   ` Ralph Hempel
2008-06-21 18:58     ` cuicui
2008-06-21 14:45 ` Dave Korn
2008-06-21 18:29   ` Ralph Hempel
2008-06-22 17:16   ` Reini Urban
2008-06-22 18:17     ` Dave Korn
2008-06-23  7:05     ` Ralph Hempel
2008-06-23  8:42       ` Dave Korn
2008-06-23 12:20         ` Ralph Hempel
2008-06-23 12:37           ` Dave Korn
2008-06-24  0:40             ` Ralph Hempel [this message]
2008-06-24  1:25               ` Ralph Hempel
2008-06-24  1:28               ` Christopher Faylor
2008-06-24  3:42                 ` Ralph Hempel

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=48603D26.2020302@bmts.com \
    --to=rhempel@bmts.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).