On Thu, Sep 15, 2011 at 12:48 AM, Thomas Rast <trast@xxxxxxxxxxxxxxx> wrote:
> Johannes Sixt wrote:
>> Even when you want to exchange your commits between two or three machines,
>> all you need is ssh access. There is no *git server* necessary. git is not
>> svn. ;-)
>
> I'd even put this somewhat more bluntly. My two-step advice on
> switching from svn to git is:
>
> 1) forget *everything* you know from SVN
> 2) learn git as usual
>
> I don't hang out on IRC as much any more, so maybe it got better. But
> 90%[*] of SVN convert's problems seem to stem from some preconceived
> notions they carried over from SVN.
>
> Such as, "HEAD is the newest commit". Or the whole centralized
> vs. distributed you mentioned.
>
>
>
> [*] 78% of all statistics were made up on the spot
>
> --
> Thomas Rast
> trast@{inf,student}.ethz.ch
>
How can I "learn git as usual"?
I don't think I was on Subversion long enough to permanently damage my
brain. Only a few months (actually . . . that's probably enough). I
never used it's branching, tagging or merging features. Commit and
revert were the only that I used. Regardless, I'm happy to forget
everything I know about Subversion.
I've watched Linus Torvalds tech talk on git:
http://www.youtube.com/watch?v=4XpnKHJAok8
I also read four and a half chapters of Pro Git pdf:
http://progit.org/ebook/progit.pdf
I read and understood git for computer scientists:
http://eagain.net/articles/git-for-computer-scientists/
So I have a pretty good understanding why git is THE superior source
code management choice. And I have a basic understanding of how git
works. I know how to install a *nix server and can survive on the
CLI.
Here's where I think I'm having some troubles, and maybe you can help
me identify any others:
I got confused in Chapter 5 of the Pro Git pdf book, trying to discern
what needs to be done on the server, and what needs to be done on the
work station. The chapter seems to jump around a bit, and doesn't
follow a linear pattern. Maybe I need to read it more carefully?
Also, I'm not clear on the best way to manage large numbers of git
users (like 12-24), who also may have permissions to other services as
well (ftp, databases, email, etc). I have some hesitancy creating
each one manually on the CLI.
Finally, I'm not sure how to "learn git as usual". Point me in the
right direction, please.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html