From: Eric Blake <ebb9@byu.net>
To: srinivas naga vutukuri <srinivas.vutukuri@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git 1.4.4.2 is giving the following errors...
Date: Thu, 21 Dec 2006 06:03:59 -0700 [thread overview]
Message-ID: <458A863F.10700@byu.net> (raw)
In-Reply-To: <ace3f33d0612202115p3fedb169pf235c4556f2eef57@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
According to srinivas naga vutukuri on 12/20/2006 10:15 PM:
> Hi,
>
> I am new to git.
>> From the web site downloaded the 1.4.4.2 source and compiled on the
> cygwin environment.
Why not download the pre-compiled git 1.4.4.3 from cygwin, rather than
building it yourself?
> when am trying as an example to use the git,
>
> ------------------------------------snip----------------------------------------------------------
>
> sh-3.2$ git clone git://git.kernel.org/pub/scm/git/git.git
> : command not foundclone: line 7:
I wonder if you are suffering from corrupted line endings. If your
scripts end up with DOS line endings, but you execute them on a cygwin
binary mount, then bash will happily treat those \r as literal characters
rather than ignored whitespace (similarly to how bash behaves on Linux
with \r characters, except that on Linux, people tend to not use DOS line
endings).
- --
Life is short - so eat dessert first!
Eric Blake ebb9@byu.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFioY/84KuGfSFAYARAiNEAJ942dcJyv4v2uYWd5NI7y43JeL9FQCeMMyH
GGOX9k8mTra+K19nxv9qqDw=
=RWS0
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2006-12-21 13:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-21 5:15 git 1.4.4.2 is giving the following errors srinivas naga vutukuri
2006-12-21 5:29 ` Junio C Hamano
2006-12-21 13:03 ` Eric Blake [this message]
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=458A863F.10700@byu.net \
--to=ebb9@byu.net \
--cc=git@vger.kernel.org \
--cc=srinivas.vutukuri@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).