From: steven Loker <stevenlokerr@gmail.com>
To: git@vger.kernel.org
Subject: Re: Path Too Long fix
Date: Tue, 19 Mar 2013 00:20:44 -0700 (PDT) [thread overview]
Message-ID: <1363677644062-7580026.post@n2.nabble.com> (raw)
In-Reply-To: <3214ab99-ad65-4c97-839f-a6210e74e868@i39g2000prd.googlegroups.com>
Just fix it by downloading longPathTool. It works on my file since i dont
have time Copypasting,moving and renaming files.no hassle.
http://LongPathTool.com <http://LongPathTool.com>
--
View this message in context: http://git.661346.n2.nabble.com/Path-Too-Long-fix-tp6156555p7580026.html
Sent from the git mailing list archive at Nabble.com.
parent reply other threads:[~2013-03-19 7:21 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <3214ab99-ad65-4c97-839f-a6210e74e868@i39g2000prd.googlegroups.com>]
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=1363677644062-7580026.post@n2.nabble.com \
--to=stevenlokerr@gmail.com \
--cc=git@vger.kernel.org \
/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).