From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: git 2.8.3 spurious output
Date: Wed, 08 Jun 2016 13:56:00 -0000 [thread overview]
Message-ID: <6bf93b8d-3fab-f138-4a94-00b6f65340cf@cornell.edu> (raw)
In-Reply-To: <1a74892a-8d3d-24fb-8a3b-b3fbb35c96b9@cornell.edu>
On 6/8/2016 9:45 AM, Ken Brown wrote:
> On 6/8/2016 5:35 AM, Cufi, Carles wrote:
>> Hi,
>>
>> When running git 2.8.3 with certain of its commands (submodule for
>> example) I get spurious output on the terminal:
>>
>> cacu ~/src/nordic/gh/pc-ble-driver-py (master)
>> $ git submodule deinit .
>> ': not a valid identifiertext.sh: line 88: export: `displaypath
>> Cleared directory ''
>> ': not a valid identifiertext.sh: line 88: export: `name
>> ': not a valid identifiertext.sh: line 88: export: `url
>> ': not a valid identifiertext.sh: line 88: export: `displaypath
>> Submodule '' () unregistered for path ''
>>
>> The variables referenced above (displaypath, name, url) seem to be
>> part of the git-submodule script in /usr/libexec/git-core.
>
> It looks like output lines are being overwritten, which suggests that
> you have DOS line endings somewhere (maybe in git-submodule?). For
> example, there seems to be a reference to line 88 of gettext.sh,
> partially overwritten by something else. (Notice that git-submodule
> calls eval_gettext many times; the latter is defined in
> /usr/bin/gettext.sh.)
^^ at line 88
--
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
next prev parent reply other threads:[~2016-06-08 13:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-08 9:35 Cufi, Carles
2016-06-08 13:45 ` Ken Brown
2016-06-08 13:56 ` Ken Brown [this message]
2016-06-08 13:57 Cufi, Carles
2016-06-08 14:06 ` Ken Brown
2016-06-08 14:19 Cufi, Carles
2016-06-08 14:27 ` Ken Brown
2016-06-08 14:33 ` Warren Young
2016-06-08 14:41 Cufi, Carles
2016-06-08 16:45 ` Achim Gratz
2016-06-09 7:52 Cufi, Carles
2016-06-09 19:37 ` Warren Young
2016-06-11 19:20 ` Brian Inglis
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=6bf93b8d-3fab-f138-4a94-00b6f65340cf@cornell.edu \
--to=kbrown@cornell.edu \
--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).