Git please!

See also a Google Code Hosting developer's response in  issue 415 
<http://code.google.com/p/support/issues/detail?id=415#c5>: "We have no intention of
supporting additional version control systems any time in the near future."

I vote for Git support.

Bazaar <http://www.bazaar-vcs.org>, please!

(No comment was entered for this change.)

(No comment was entered for this change.)

It would be amazing to have Google support Git.

It would be amazing for git to support http well.  ;-)

I vote for Mercurial and git!

+1 vote

+1 for git. Maybe you could look at RubyForge (GForge-based) which offers git in
addition to svn. 

Another vote for git.

Mercurial support would be great.

Mercurial plzthx. Git is my #2.

+1 for git

+1 for git

git please!!!!

+1, really. I like every piece of code.google.com, except SVN.
Git or Mercurial!

+1 mercurial

Stop saying +1! Star the issue instead.

then split the issue for mercurial and git, so people can just star.

the problem with starring is that you keep receiving this idiotic +1 comments by email.
so we say +1 instead.

oh, and btw, +1 for git  ;)

You got it backwards: the problem with idiotically saying +1 is that people who 
starred it will get those idiotic comments.

hehe, I know.
I was trying some sarcasm there.. sorry.

I starred the issue months ago, and the +1's are really annoying.

Anyway, this is not a place for a chat, but to talk about the issue.
So I'll shut my mouth now. Bye.

Perhaps Google can just buy github.com; the kind of features that I miss on their
site (wiki, issue tracking, code review) can be found on Google project hosting and
vice verse (git, nice looks, the 'social thing', charts that show branching and
merging history). 

I would love to know what Google's "budget" is for code hosting, in terms of man
power and money. If it is small, then perhaps the priority should be to migrate it to
the App Engine and open source it. 

When I star, I keep receiving those +1, but if I say it myself, other people receive
my +1...
btw, +1 for mercurial ;)

+1 git

+1 for git

(No comment was entered for this change.)

In progress.

Sweet!

yay! awesome

The question is is google working on git or mercurial or both?

I guess you'll have to wait and see.  ;-)

I think there are clean "bridges" between both anyway. (unlike between git/hg and 
svn, which can never be bridged in a perfect way)

+1 for git. 

+1

Given that Android source is hosted on GIT, I can only imagine that it's just a matter of time now.

http://tr.im/android_git

Yeah! :) git git git

Mercurial!

Bazaar, please. The only one with true rename...

I'm sorry? Mercurial has true renames, too.

I don't wanna start a flame war here... Maybe it depends on what "true rename" means 
to you. 

I tested both. At the time, only Bazaar implemented rename operation as I expected (not 
just copy+delete but a regular file/directory rename in file manager's sense); and could 
also rename directories. 
http://bazaar-vcs.org/BzrFeatures

(I am Java developer, I refactor a lot, I need this everyday.)

Mercurial implements rename as copy+delete and does not even recognize directories, only 
file names... For me, disappointment.

I don't think that offer distributed version control systems support other than 
Subversion is a good idea.
It make developers have to control more VCS, unless google code host would support 
auto sync the source in the multiple version control systems.

Subversion is NOT a distributed VCS, but a centralized one.

Amazing..... google is gonna support distributed version control system ... i dont 
have words to describe how happy i am...

i love you google !

@patrikbeno: From a merge standpoint, a rename or a copy/delete at the file level are the same. But it's true 
Mercurial infers directory renames from the fact that all files in a dir have been renamed. One can construct 
corner cases  where this leads to the wrong thing, but in my fairly long experience with Mercurial this has not 
ever bitten me, and I refactor Java code a lot. And it's also true that Mercurial does not have space-efficient 
renames in the history (there the "add with hint where it was copied from" and delete hurts a bit). I know bzr 
tracks dir renames explicitly. Don't know how it handles renames space-wise in the history.

@peter: Yes, but merge is NOT all I need from version control.

My typical example is this: you have 'src' directory with 512 source files and you 
rename it to 'sources'. 
Now in, subversion and similar copy&delete systems, you see at least 512 deletes and 
512 adds/inserts.
In bazaar, you see what you did: renamed: src -> sources

As for you space handling concerns, no copy&delete system can handle renames as 
efficiently as the system that supports renames as first class citizens.

What bothers me more with copy&delete renames is history: How can you know that this 
change represents rename-single-directory operation if what you see is 512 deletes 
and 512 inserts?

(Anyway, this is certainly the wrong place for this discussion.)

My Vote for Mercurial

I don't recall Google saying this was a poll for what system to implement...

They probably already chose a DVCS, since they are already working on it. As sussman
said, "you'll have to wait and see".

Wonder how long this'll take to implement. We've all needed this for a _long_ time heh..

Hope its not too long.. considering its the number one _real_ request.. (I dont
consider the +1 thing being anything that should take long to "fix".. its just people
being stupid hehe).

We have top men working on it.

Top.
Men.

No need to rush it.
Let it take it's time.

True, i spose we can always use something other than Google Code until the DVCS
comes.. ;)

But in all seriousness, i am very excited about this. Google Code is one of the best
hosts imo, its got a great simplistic design. The only problem was, and still is, the
horrible VCS, but hopefully that will change in the near future.

Really nice, but what DVCS is google going to use? I vote for bazaar.

The new "+1" preventing feature in action, hehe.

git please

When did anyone from Google say this was a poll for which DVCS to implement??

Google is already working on it, which means they already decided on a DVCS system. 
When you say "<some dvcs> please" or "+1 for <some dvcs>", you're just annoying the 
140 people who starred this issue. It won't change anything, because it was already 
decided.

yeah nicolas.alvarez is right... it just annoys when this issue fills up my inbox

I hope you're being sarcastic.   :)

Anyway, why don't you un-star the issue already?
It's already accepted and being worked on, it won't make a difference.

Mercurial is launched on Google Code: 
http://google-code-updates.blogspot.com/2009/04/mercurial-support-for-project-hosting.html

thank you!!!! 

Great news. Thanks.

w00t! you rock!!!

A bit disappointed it wasn't git, but thanks anyway.
Any distributed VCS is way better than SVN.

Unfortunately, it's a bit late (for me, anyway).
Github announced *yesterday* that they finally released the issue tracking thing, the
only item they were missing for project hosting.

Ditto what Rodolfo said. Wish you had announced it before I discovered 
bitbucket.org (it's like github but for Mercurial, and has always had wiki and 
issue tracking).