From: Sebastian Schuberth <sschuberth@gmail.com>
To: Johannes Sixt <j6t@kdbg.org>
Cc: worldhello.net@gmail.com,
Thomas Braun <thomas.braun@virtuell-zuhause.de>,
Git Mailing List <git@vger.kernel.org>,
msysGit Mailinglist <msysgit@googlegroups.com>
Subject: Re: Same test-path-utils behaves differently on different Windows systems
Date: Thu, 10 Oct 2013 22:47:04 +0200 [thread overview]
Message-ID: <CAHGBnuOHD1o1si9EMpi+qi=VDCvAgEQbLfNaVDfOS983E6AKuw@mail.gmail.com> (raw)
In-Reply-To: <52570860.3060503@kdbg.org>
On Thu, Oct 10, 2013 at 10:04 PM, Johannes Sixt <j6t@kdbg.org> wrote:
>> PS: I'm also quite unhappy about naming the function "mingw_path". The
>> path mangling comes from MSYS, not MinGW, so if at all it should be
>> named msys_path. But as the code for the "mingw_path" function does
>> nothing either MSYS or MinGW related but just prints argv[2] as it was
>> passed to main() it should probably simply called "print_path".
>
> You have a point here. If it were to change, "echo_path" would be my
> preference.
I'll stick to "print_path" as it more closely resembles "pwd", *print*
working directory.
--
Sebastian Schuberth
next prev parent reply other threads:[~2013-10-10 20:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-10 12:13 Same test-path-utils behaves differently on different Windows systems Sebastian Schuberth
2013-10-10 15:52 ` Sebastian Schuberth
2013-10-10 17:57 ` Johannes Sixt
2013-10-10 19:47 ` Sebastian Schuberth
2013-10-10 20:04 ` Johannes Sixt
2013-10-10 20:27 ` Sebastian Schuberth
2013-10-10 20:47 ` Sebastian Schuberth [this message]
2013-10-15 14:54 ` wwiser
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='CAHGBnuOHD1o1si9EMpi+qi=VDCvAgEQbLfNaVDfOS983E6AKuw@mail.gmail.com' \
--to=sschuberth@gmail.com \
--cc=git@vger.kernel.org \
--cc=j6t@kdbg.org \
--cc=msysgit@googlegroups.com \
--cc=thomas.braun@virtuell-zuhause.de \
--cc=worldhello.net@gmail.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 NNTP newsgroup(s).