On Apr 24, 4:27 pm, Stuart Sierra <the.stuart.sie...@gmail.com> wrote:
> On Apr 24, 5:16 pm, e <evier...@gmail.com> wrote:
>
> > But let me understand ... when you do a commit, you haven't really
> > done anything that "counts"?  Loaded question, I know, but it seems like you
> > have to do a commit, and then do a "send" or something, to actually share
> > your changes.  Is that right?
>
> Sort of.  First you "git add", which puts changes in the "staging
> area" of your local repository.  Then you "git commit", which records
> a commit, still in your local repository.  Then you "git push" to copy
> your commits to the remote repository (usually called "origin").
>
> Everything counts, and nothing counts, since git allows you to delete
> or undo almost anything, including commits in the remote repository.
> That's actually one of the reasons Google gives for not supporting git
> -- all that freedom makes it hard to re-implement git on top of their
> infrastructure.
>
> -Stuart Sierra

Yes, Git has superpowers. We're a Git shop, and I haven't used Hg at
all, but after most of a year now using Git, it's a super powerful
tool. We migrated from SVN and have no regrets whatsoever.

I think the main consideration in choosing a SCM  ought to be making
Rich's job manageable. The model of Clojure development is a lot like
Linux, with Rich as Linus. They both are the ultimate merge master,
and managing branches and merging is what Git is all about.  Linus
wrote Git with this use case in mind. Hg and bzr probably have similar
capabilities. But I can attest to how easy Git makes it to manage some
amazingly tangled graphs.


Hugh





--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To post to this group, send email to clojure@googlegroups.com
To unsubscribe from this group, send email to 
clojure+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/clojure?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to