git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Sixt <j.sixt@viscovery.net>
To: Chris Hoffman <chris.c.hoffman@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git-daemon on Windows?
Date: Wed, 11 Jun 2008 15:54:02 +0200	[thread overview]
Message-ID: <484FD8FA.3060003@viscovery.net> (raw)
In-Reply-To: <63c5d3820806110551y69e895eeg4fde4bfdaf22bbf2@mail.gmail.com>

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

  parent reply	other threads:[~2008-06-11 13:56 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 [this message]
2008-06-12 15:23   ` John Yesberg
2008-06-12 18:24     ` Chris Hoffman

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=484FD8FA.3060003@viscovery.net \
    --to=j.sixt@viscovery.net \
    --cc=chris.c.hoffman@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).