On Thu Mar 08 12, Tom Haws wrote:
Keith,
Git is magic and it will make all your troubles go away. Really. I am
speaking from real world before-and-after experience with two
clients/projects in the past two years. Call me and we can discuss it
480-201-5476. And you can also start by
please what troubles will disapear?
On Thu, Mar 22, 2012 at 2:13 AM, Gerard Snitselaar d...@snitselaar.orgwrote:
On Thu Mar 08 12, Tom Haws wrote:
Keith,
Git is magic and it will make all your troubles go away. Really. I am
speaking from real world before-and-after experience with
Specifically the trouble you have being able to collaborate with others
because you feel you have to wait on others to finish their edits before
you can work on the code base, that trouble will go away partly because Git
is super smart and partly because Git has something no other package (even
funny guy!
On Thu, Mar 22, 2012 at 7:10 AM, Tom Haws tom.h...@gmail.com wrote:
and I was blessing the name of Git all the way.
---
PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change your
Oops. Pun not noted previously. No wonder that rolled off the tongue so
well. :-D
--
To forgive is the highest, most beautiful form of love. In return, you
will receive untold peace and happiness. - Dr. Robert Muller
On Thu, Mar 22, 2012 at 10:11 AM, Michael Havens bmi...@gmail.com wrote:
modifications to an existing
system without spending a lot of time coordinating.
Keith Smith
--- On *Wed, 3/7/12, Alan Dayley aday...@gmail.com* wrote:
From: Alan Dayley aday...@gmail.com
Subject: Re: GIT and Github - howto.
To: Main PLUG discussion list plug-discuss
Hi,
I have GIT installed on my server and I have Github. I understand the
versioning part. The concept I am having trouble grasping is how I can use it
a collaboration tool.
It is just me and another programmer. We both have a local dev environment.
We work out of our homes and we
Git doesn't really allow file locking. You'd have to have some good
communication to prevent working on the same file. Or... You can use the
merge process. If the other person updates a file, pushes to the repo, and
you try to pull it in after you've updated same file, you will be told you
and Github - howto.
To: Main PLUG discussion list plug-discuss@lists.plug.phoenix.az.us
Date: Wednesday, March 7, 2012, 4:51 PM
Git doesn't really allow file locking. You'd have to have some good
communication to prevent working on the same file. Or... You can use the
merge process
code so others cannot modify the file.
Keith Smith
--- On *Wed, 3/7/12, James Mcphee jmc...@gmail.com* wrote:
From: James Mcphee jmc...@gmail.com
Subject: Re: GIT and Github - howto.
To: Main PLUG discussion list plug-discuss@lists.plug.phoenix.az.us
Date: Wednesday
From: keith smith klsmith2...@yahoo.com
Thanks James. What is everyone else doing[?] I'm sure others have
had the problem of needing to check out code so others cannot
modify the file.
Lock-modify-check in-unlock is the old way, dude. You can *do* that using
SVN, but you're discouraged from
.
Keith Smith
--- On Wed, 3/7/12, Alan Dayley aday...@gmail.com wrote:
From: Alan Dayley aday...@gmail.com
Subject: Re: GIT and Github - howto.
To: Main PLUG discussion list plug-discuss@lists.plug.phoenix.az.us
Date: Wednesday, March 7, 2012, 5:31 PM
The need for source file locking is often
Subject: Re: GIT and Github - howto.
To: Main PLUG discussion list plug-discuss@lists.plug.phoenix.az.us
Date: Wednesday, March 7, 2012, 5:43 PM
From: keith smith klsmith2...@yahoo.com
Thanks James. What is everyone else doing[?] I'm sure others have
had the problem of needing to check out code
:
From: Alan Dayley aday...@gmail.com
Subject: Re: GIT and Github - howto.
To: Main PLUG discussion list plug-discuss@lists.plug.phoenix.az.us
Date: Wednesday, March 7, 2012, 5:31 PM
The need for source file locking is often an indicator of a problem. Three
likely ones:
1. Developers
14 matches
Mail list logo
