From: "Chris Hoffman" <chris.c.hoffman@gmail.com>
To: "John Yesberg" <john.yesberg@gmail.com>
Cc: "Johannes Sixt" <j.sixt@viscovery.net>, git@vger.kernel.org
Subject: Re: git-daemon on Windows?
Date: Thu, 12 Jun 2008 14:24:50 -0400 [thread overview]
Message-ID: <63c5d3820806121124p490ecf3eh87cb7c3742937fb2@mail.gmail.com> (raw)
In-Reply-To: <1033a22d0806120823j40185f9dj28672803490f8bdb@mail.gmail.com>
Yes, I think that this is a very good section of the tutorial to
consult. It is just hard for me to beat back my subversion thinking.
On Thu, Jun 12, 2008 at 11:23 AM, John Yesberg <john.yesberg@gmail.com> wrote:
> I'm trying to learn about this too.
> I found the gittutorial
> http://www.kernel.org/pub/software/scm/git/docs/gittutorial.html
> useful.
> See the section "Using git for collaboration", which explains how use
> can use a shared filesystem.
>
> Or maybe I don't understand the subtleties of the issue.
>
> John.
>
> On Wed, Jun 11, 2008 at 2:54 PM, Johannes Sixt <j.sixt@viscovery.net> wrote:
>> Chris Hoffman schrieb:
>>> Is there a distribution of the git server for Windows, or am I totally
>>> missing the point of git? Will a simple file share work, or do I have
>>> to worry about file locking and such (e.g., two people try to commit
>>> at the same time).
>>
>> You are missing *some* point of git: Usually, everyone has his own
>> repository, hence, commits that happen concurrently won't be a problem.
>>
>> But you must exchange your work, and for this it is common that everyone
>> in addition has a publically accessible (bare) repository. These you can
>> place on a normal file share. I do this all the time.
>>
>> You *can* choose to have only a single (bare) repository that everyone
>> uses to exchange work. But then you do have to worry about concurrent
>> *pushes* that get in the way of each other. You have this problem no
>> matter which form of server you chose (file share, ssh, git daemon,
>> WebDAV). If you go this route, you need a policy how people publish their
>> work (eg. branch namespaces). msysgit and 4msysgit do it this way.
>>
>> -- Hannes
>> --
>> To unsubscribe from this list: send the line "unsubscribe git" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>
prev parent reply other threads:[~2008-06-12 18:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-11 12:51 git-daemon on Windows? Chris Hoffman
2008-06-11 13:27 ` Jakub Narebski
2008-06-11 16:41 ` Avery Pennarun
2008-06-11 13:54 ` Johannes Sixt
2008-06-12 15:23 ` John Yesberg
2008-06-12 18:24 ` Chris Hoffman [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=63c5d3820806121124p490ecf3eh87cb7c3742937fb2@mail.gmail.com \
--to=chris.c.hoffman@gmail.com \
--cc=git@vger.kernel.org \
--cc=j.sixt@viscovery.net \
--cc=john.yesberg@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).