Re: What VCS do you use with xCode?
Re: What VCS do you use with xCode?
- Subject: Re: What VCS do you use with xCode?
- From: Panagiotis Atmatzidis <email@hidden>
- Date: Mon, 23 Mar 2009 20:14:29 +0200
On 23 Μαρ 2009, at 5:24 ΜΜ, Andrew Keller wrote:
On Mar 22, 2009, at 3:14 PM, Panagiotis Atmatzidis wrote:
Yes I know, I set up an SVN in no-time while it took me 3 hours to
setup correctly Git . The problem with git+dreamhost is that... the
webdav howto does not work and the ssh way works nicely but it
means that I will have to give access to my $HOME to another user
with my user/pass which I dislike.
I have had much success with using a web server for publishing a git
repository.
Place a bare clone of your repository on a public website, and run
"git update-server-info" inside it. Poof. It is now available as
read-only via HTTP with no plugins required. To maintain the public
version, just push your changes to it. The disadvantage is, as far
as I've found, you have to run "git update-server-info" every time
you push to it.
Git also comes with a daemon that is intended to provide read-only
access to repositories on the local machine, but I haven't played
with it. I do know that you don't have to run "git update-server-
info" on it – It's just supposed to work. I believe the Linux
kernel is published like this.
Also keep in mind that although you *can* have a centralized server
with Git (which is nice for one person), you do not have to use
one. When you begin to incorporate multiple people, commit access
becomes a major issue. This is where we take advantage of Git being
a distributed filesystem. It is intended that people pull from each
other, rather than a centralized server. In other words, everyone
in your group needs their own public server. Technically, they
could just be different accounts on the same server, but it doesn't
matter. All that matters is that only they have commit access to a
public clone of their repository, which is then available as read-
only to everyone else. When a person in the group wants his or her
changes to be publicly available, just push to the publicly
available clone, and then everyone else can pull from there.
If my memory serves, then I believe it took me a few hours to figure
out how to set up git on OS X. After that, I just wrote a shell
script in 10 minutes and distributed that to the rest of my
computers. These days, instructions exist online that are very easy
to follow. In the end, the initial setup time was totally worth it.
I don't know about other versioning systems, but Git also does data
verification. It's saved me twice since I started using it. It
also lead me to finding some bad memory.
HTH -
Andrew Keller _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
Thanks for the pointers Mr Keller! I think I'll give a deeper look,
because from what I've read about it, Git seems perfect for the task.
Best regards
Panagiotis (atma) Atmatzidis
email: email@hidden
URL: http://www.convalesco.org
--
The wise man said: "Never argue with an idiot. They bring you down to
their level and beat you with experience."
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden