public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: LRN <lrn1986@gmail.com>
To: cygwin@cygwin.com
Cc: Yaakov Selkowitz <yselkowitz@cygwin.com>
Subject: Re: cygwin port of glib
Date: Thu, 11 Apr 2019 11:51:00 -0000	[thread overview]
Message-ID: <97eea578-40e1-8cf3-2f63-aebeb426f408@gmail.com> (raw)
In-Reply-To: <18ed9090-2c35-cca2-4b7f-2d057a44b351@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1531 bytes --]

On 03.04.2019 15:16, LRN wrote:
> On 05.03.2019 17:23, LRN wrote:
>> On 05.03.2019 17:07, E. Madison Bray wrote:
>>>
>>> If they're clean, worthwhile patches then I absolutely think you
>>> should get them integrated upstream if at all possible--that's almost
>>> always preferable.
>>
>> Okay, i'll see what i can do.
>>
> 
> Made some progress, but i would benefit from some input on a few things.
> 
> 1) This[0] cygwinports commit and a related gnulib[1] commit. Which version of
> cygwin (CYGWIN_VERSION_API_MINOR) corresponds to 1.7 (is the 1.7 number even
> correct?). As a less-intrusive fix, i can switch
> #ifdef __CYGWIN__
> to
> #if defined(__CYGWIN) && (!defined (CYGWIN_VERSION_API_MINOR) ||
> CYGWIN_VERSION_API_MINOR < somevalue)
> 
> 
> 2) This[2] cygwinports commit. I don't quite get what the author means. Does he
> mean that returning a path that looks like "//etc" from parsing a URI
> "file:////etc" is correct? Or the opposite, that it should return "/etc" ? The
> commit seems to be saying one thing, while the code does something else.
> 
> 
> [0]:
> https://github.com/cygwinports/glib2.0/commit/b61abed9554ab813ed358ea5bad648987573772e#diff-2d64c930085856723abe9a40105389abR256
> 
> [1]:
> https://git.savannah.gnu.org/cgit/gnulib.git/commit/lib/localcharset.c?id=9f5ab735f030faf651961d55ce3b849dd56dcff3
> 
> [2]:
> https://github.com/cygwinports/glib2.0/commit/40ca93c8ae81e7a05ec098246b43ce74e157ebd6#diff-c86c0d1edc7cdc043b8b01ee6e526817
> 

Hello? Anybody?


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2019-04-11 11:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-03 10:07 LRN
2019-03-05 14:07 ` E. Madison Bray
2019-03-05 14:23   ` LRN
2019-04-03 12:16     ` LRN
2019-04-11 11:51       ` LRN [this message]
2019-04-17 17:43       ` [Attn. Maintainer] glib2.0 LRN

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=97eea578-40e1-8cf3-2f63-aebeb426f408@gmail.com \
    --to=lrn1986@gmail.com \
    --cc=cygwin@cygwin.com \
    --cc=yselkowitz@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).