Thanks Matt and Dave and everyone else for your feedback on this.
Ok, I've done some more reading in the Pro Git manual and I think I have an
idea of how to get started. Could I run this by you just in case I'm missing
anything? Currently (pre-git status) what we have is two developers both
...@mhseitz.onmicrosoft.com]
Sent: Friday, January 18, 2013 12:52 AM
To: Lang, David; David Lang
Cc: Konstantin Khomoutov; Jeff King; git@vger.kernel.org; Stephen Smith
Subject: RE: Question re. git remote repository
From: git-ow...@vger.kernel.org [git-ow...@vger.kernel.org] on behalf of Lang,
David
What I would do is to have each developer have their own local copy that they
are working on.
I would then find a machine that is going to be on all the time (which could be
a developer's desktop), and create a master repository there. Note that if this
is on a developers desktop, this needs
David Lang da...@lang.hm writes:
What I would do is to have each developer have their own local copy
that they are working on.
I would then find a machine that is going to be on all the time (which
could be a developer's desktop), and create a master repository
there. Note that if this is
On Fri, 18 Jan 2013, Junio C Hamano wrote:
David Lang da...@lang.hm writes:
What I would do is to have each developer have their own local copy
that they are working on.
I would then find a machine that is going to be on all the time (which
could be a developer's desktop), and create a
David Lang da...@lang.hm writes:
On Fri, 18 Jan 2013, Junio C Hamano wrote:
David Lang da...@lang.hm writes:
...
developers then do their work locally, and after a change has been
reviewed, pull it into the master repository.
s/pull it into/push it into/; I think.
fair enough, I always
From: David Lang da...@lang.hm
Sent: Friday, January 18, 2013 9:27 PM
On Fri, 18 Jan 2013, Junio C Hamano wrote:
David Lang da...@lang.hm writes:
What I would do is to have each developer have their own local copy
that they are working on.
If you have a third machine to host the bare
@vger.kernel.org; Lang, David
Subject: Re: Question re. git remote repository
On Wed, 16 Jan 2013, Stephen Smith wrote:
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
: Konstantin Khomoutov; Jeff King; git@vger.kernel.org; Lang, David
Subject: Re: Question re. git remote repository
On Wed, 16 Jan 2013, Stephen Smith wrote:
Ideally we'd prefer to simply create our remote repository on a
drive of one of our local network servers. Is this possible?
Yes
On Wed, Jan 16, 2013 at 03:00:41PM -0800, David Lang wrote:
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
From: git-ow...@vger.kernel.org [git-ow...@vger.kernel.org] on behalf of Lang,
David [david.l...@uhn.ca]
I thought the idea was that each developer installed git locally on their
machines
Yes.
and (as needed) committed their changes to the master repository which
resides externally to
On Fri, 18 Jan 2013, Matt Seitz wrote:
From: git-ow...@vger.kernel.org [git-ow...@vger.kernel.org] on behalf of Lang,
David [david.l...@uhn.ca]
The other David Lang (da...@lang.hm) believes that using git push using NFS or CIFS/SMB
may not be safe and reliable. Based on the following
Hello,
We're just in the process of investigating a versioning tool and are very
interesting in git. We have one question we're hoping someone can answer. In
regards to the repositories, I think I understand correctly that each developer
will have a local repository that they will work from,
On Wed, 16 Jan 2013 17:49:09 +
Lang, David david.l...@uhn.ca wrote:
We're just in the process of investigating a versioning tool and are
very interesting in git. We have one question we're hoping someone
can answer. In regards to the repositories, I think I understand
correctly that each
On Wed, Jan 16, 2013 at 10:06:15PM +0400, Konstantin Khomoutov wrote:
In regards to the repositories, I think I understand correctly that
each developer will have a local repository that they will work
from, and that there will also be a remote repository (origin) that
will hold the
On Wed, 16 Jan 2013 10:21:56 -0800
Jeff King p...@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
Hi David, now we are going to have some confusion here, two David Langs on the
list :-)
On Wed, 16 Jan 2013, Lang, David wrote:
We're just in the process of investigating a versioning tool and are very
interesting in git. We have one question we're hoping someone can answer. In
regards to
Konstantin Khomoutov kostix+...@007spb.ru wrote in message
news:20130116233744.7d0775eaec98ce154a9de...@domain007.com...
On Wed, 16 Jan 2013 10:21:56 -0800
Jeff King p...@peff.net wrote:
I agree that performance is not ideal (although if you are on a fast
LAN, it probably would not
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
On Wed, 16 Jan 2013, Stephen Smith wrote:
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
David Lang da...@lang.hm wrote in message
news:alpine.deb.2.02.1301161459060.21...@nftneq.ynat.uz...
But if you try to have one filesystem, with multiple people running git on
their
machines against that shared filesystem, I would expect you to have all sorts
of
problems.
What leads you
On Wed, 16 Jan 2013, Matt Seitz (matseitz) wrote:
David Lang da...@lang.hm wrote in message
news:alpine.deb.2.02.1301161459060.21...@nftneq.ynat.uz...
But if you try to have one filesystem, with multiple people running git on their
machines against that shared filesystem, I would expect you
From: David Lang [mailto:da...@lang.hm]
On Wed, 16 Jan 2013, Matt Seitz (matseitz) wrote:
Linus seemed to think it should work:
http://permalink.gmane.org/gmane.comp.version-control.git/122670
In the link you point at, he says that you can have problems with some
types of
actions.
On Thu, 17 Jan 2013, Matt Seitz (matseitz) wrote:
From: David Lang [mailto:da...@lang.hm]
On Wed, 16 Jan 2013, Matt Seitz (matseitz) wrote:
Linus seemed to think it should work:
http://permalink.gmane.org/gmane.comp.version-control.git/122670
In the link you point at, he says that you can
From: David Lang [mailto:da...@lang.hm]
Linus says that git does not have proper locking, so think about it,
what do
you think will happen if person A does git add a/b; git commit and person
B does
git add c/d; git commit?
Sorry, I wasn't clear. My assumption is that a shared repository
On Thu, 17 Jan 2013, Matt Seitz (matseitz) wrote:
From: David Lang [mailto:da...@lang.hm]
Linus says that git does not have proper locking, so think about it,
what do
you think will happen if person A does git add a/b; git commit and person
B does
git add c/d; git commit?
Sorry, I wasn't
From: David Lang [mailto:da...@lang.hm]
On Thu, 17 Jan 2013, Matt Seitz (matseitz) wrote:
1. a bare repository that is normally accessed only by git push and
git pull (or git fetch), the central repository model.
pulling from it would not be a problem, I could see issues with multiple
On Thu, 17 Jan 2013, Matt Seitz (matseitz) wrote:
From: David Lang [mailto:da...@lang.hm]
On Thu, 17 Jan 2013, Matt Seitz (matseitz) wrote:
1. a bare repository that is normally accessed only by git push and
git pull (or git fetch), the central repository model.
pulling from it would not
David Lang da...@lang.hm wrote in message
news:alpine.deb.2.02.1301161843390.21...@nftneq.ynat.uz...
On Thu, 17 Jan 2013, Matt Seitz (matseitz) wrote:
2. a repository where only one user does git add and git commit,
while other users will do git pull, the peer-to-peer model (you pull
29 matches
Mail list logo
