public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Henri <houder@xs4all.nl>
To: cygwin@cygwin.com
Subject: Re: cygwin_conv_path sometimes removes trailing slash
Date: Mon, 01 Feb 2016 10:59:00 -0000	[thread overview]
Message-ID: <loom.20160201T115447-915@post.gmane.org> (raw)
In-Reply-To: <CAOYw7dtaqNYHayMeXupTG10VB3DdWXt10A3EroFuPfJVVN69eA@mail.gmail.com>

Ray Donnelly <mingw.android <at> gmail.com> writes:

> I can't check as I'm at work, but to the best of my knowledge (and yes
> I wrote these a long time ago) path_conv::check is used in conversions
> both ways so I am talking about both cases here, Jan's with the first
> patch and Ken's with the second patch. Please do correct me if I am
> wrong though! I will run some detailed tests tonight.

As I wrote to Ken (private e-mail), let us wait for Corinna: she knows
all the nooks and crannies here ...

As far as I can tell, path_conv::check() is invoked for posix -> win32
only; that is, in cygwin_conv_path() (winsup/cygwin/path.cc).

But, again, let us wait for Corinna.

Regards,
Henri


--
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:[~2016-02-01 10:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-30 20:46 Ken Brown
2016-01-31 22:25 ` Jan Nijtmans
2016-02-01 10:29   ` Henri
2016-02-01 10:38     ` Henri
2016-02-01 10:45     ` Ray Donnelly
2016-02-01 10:59       ` Henri [this message]
     [not found]   ` <CAOYw7ds-N=f+JCn-2rtFqOyahmA_M9mVNwv1CZH6__M-K7ht1A@mail.gmail.com>
2016-02-08 18:13     ` Corinna Vinschen
2016-02-11 16:50       ` Ray Donnelly
2016-02-14 19:08 ` Ken Brown
2016-02-15 15:26   ` Corinna Vinschen

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=loom.20160201T115447-915@post.gmane.org \
    --to=houder@xs4all.nl \
    --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).