From: Sebastian Schuberth <sschuberth@gmail.com>
To: Emanuel Rietveld <codehotter@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Git push to samba/cifs share fails
Date: Sat, 31 Mar 2012 20:47:40 +0200 [thread overview]
Message-ID: <4F77514C.10205@gmail.com> (raw)
In-Reply-To: <4F75DDF9.8060305@gmail.com>
On 30.03.2012 18:23, Emanuel Rietveld wrote:
> I get an error message when I try to push my git repository to a share
> mounted with mount.cifs.
Hmm, I wonder if this is related to msysgit's "Cannot fetch to mapped
network drives (Samba)" issue here:
http://code.google.com/p/msysgit/issues/detail?id=130
Please note that the msysgit issue tracker is closed, so you should not
place any comments there. Post to the msysgit mailing list instead.
--
Sebastian Schuberth
next prev parent reply other threads:[~2012-03-31 18:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-30 16:23 Git push to samba/cifs share fails Emanuel Rietveld
2012-03-31 18:47 ` Sebastian Schuberth [this message]
2012-04-04 8:35 ` Emanuel Rietveld
2012-04-04 12:50 ` Sebastian Schuberth
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=4F77514C.10205@gmail.com \
--to=sschuberth@gmail.com \
--cc=codehotter@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).