From: Konstantin Khomoutov <kostix+git@007spb.ru>
To: Jeff King <peff@peff.net>
Cc: Konstantin Khomoutov <kostix+git@007spb.ru>,
"Lang, David" <David.Lang@uhn.ca>,
"'git@vger.kernel.org'" <git@vger.kernel.org>
Subject: Re: Question re. git remote repository
Date: Wed, 16 Jan 2013 23:37:44 +0400 [thread overview]
Message-ID: <20130116233744.7d0775eaec98ce154a9de180@domain007.com> (raw)
In-Reply-To: <20130116182156.GB4426@sigill.intra.peff.net>
On Wed, 16 Jan 2013 10:21:56 -0800
Jeff King <peff@peff.net> wrote:
Thanks for elaborating on the "origin" -- I intended to write up on its
special status but got distracted and sent my message missing that
bit ;-)
[...]
> > > Ideally we'd prefer to simply create our remote repository on a
> > > drive of one of our local network servers. Is this possible?
> >
> > Yes, this is possible, but it's not advised to keep such a
> > "reference" repository on an exported networked drive for a number
> > of reasons (both performance and bug-free operation).
>
> I agree that performance is not ideal (although if you are on a fast
> LAN, it probably would not matter much), but I do not recall any
> specific bugs in that area. Can you elaborate?
This one [1] for instance. I also recall seing people having other
"mystical" problems with setups like this so I somehow developed an idea
than having a repository on a networked drive is asking for troubles.
Of course, if there are happy users of such setups, I would be glad to
hear as my precautions might well be unfounded for the recent versions
of Git.
1. http://code.google.com/p/msysgit/issues/detail?id=130
next prev parent reply other threads:[~2013-01-16 19:38 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-16 17:49 Question re. git remote repository Lang, David
2013-01-16 18:06 ` Konstantin Khomoutov
2013-01-16 18:21 ` Jeff King
2013-01-16 19:37 ` Konstantin Khomoutov [this message]
2013-01-16 22:59 ` Stephen Smith
2013-01-16 23:00 ` David Lang
2013-01-17 21:53 ` Lang, David
2013-01-18 5:51 ` Matt Seitz
2013-01-18 6:18 ` David Lang
2013-01-18 18:33 ` Lang, David
2013-01-18 21:56 ` Matt Seitz
2013-01-23 19:40 ` Lang, David
2013-01-23 20:24 ` Junio C Hamano
[not found] ` <201301181833.r0IIXNGb027544@smtpb02.one-mail.on.ca>
2013-01-18 20:27 ` David Lang
2013-01-18 21:20 ` Junio C Hamano
2013-01-18 21:27 ` David Lang
2013-01-18 21:38 ` Junio C Hamano
2013-01-18 23:10 ` Philip Oakley
[not found] ` <201301172153.r0HLrUIr001039@smtpb01.one-mail.on.ca>
2013-01-17 23:19 ` David Lang
2013-01-17 23:49 ` Jeff King
2013-01-16 20:07 ` David Lang
-- strict thread matches above, loose matches on Subject: below --
2013-01-16 21:07 Matt Seitz (matseitz)
2013-01-16 23:32 Matt Seitz (matseitz)
2013-01-17 0:21 ` David Lang
2013-01-17 1:09 ` Matt Seitz (matseitz)
2013-01-17 1:26 ` David Lang
2013-01-17 1:46 ` Matt Seitz (matseitz)
2013-01-17 1:59 ` David Lang
2013-01-17 2:25 ` Matt Seitz (matseitz)
2013-01-17 2:49 ` David Lang
2013-01-17 5:20 Matt Seitz
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=20130116233744.7d0775eaec98ce154a9de180@domain007.com \
--to=kostix+git@007spb.ru \
--cc=David.Lang@uhn.ca \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).