public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Pavel Fedin <p.fedin@samsung.com>
To: 'Andrew Schulman' <schulman.andrew@epa.gov>, cygwin@cygwin.com
Subject: RE: [PATCH] Fix optional variables in libargp
Date: Wed, 24 Jul 2013 09:56:00 -0000	[thread overview]
Message-ID: <001301ce8836$33a165f0$9ae431d0$%fedin@samsung.com> (raw)
In-Reply-To: <0a2tu8p6ddvgut5nqgc12292oqtihs9du5@4ax.com>

 Hello!

> Sorry, this was my fault.  I accidentally mangled your patch when I
> took PREFIX out.  I fixed that, and it works fine in x86 now.

 Good.
 Please don't forget that packages which make use of libargp (if there are
any) have to be recompiled against new argp.h in order to take advantage of
the fix.

Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia



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

  reply	other threads:[~2013-07-24  6:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-11 10:17 libargp: argp_program_version does not work Fedin Pavel
2013-07-11 16:35 ` Andrew Schulman
2013-07-11 22:02   ` Andrew Schulman
2013-07-12 14:52     ` Fedin Pavel
2013-07-12 15:36       ` Andrew Schulman
2013-07-17  9:57         ` [PATCH] Fix optional variables in libargp Fedin Pavel
2013-07-17 12:59           ` Eric Blake
2013-07-22  7:33           ` Andrew Schulman
2013-07-22  8:12             ` Pavel Fedin
2013-07-22 13:19             ` Pavel Fedin
2013-07-23 15:07               ` Andrew Schulman
2013-07-24  9:56                 ` Pavel Fedin [this message]
2022-02-18 13:30               ` Andrew Schulman

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='001301ce8836$33a165f0$9ae431d0$%fedin@samsung.com' \
    --to=p.fedin@samsung.com \
    --cc=cygwin@cygwin.com \
    --cc=schulman.andrew@epa.gov \
    /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).