(No comment was entered for this change.)

We announced mercurial support last week, see the blog post at
http://google-code-updates.blogspot.com/2009/04/mercurial-support-for-project-hosting.html

We have no plans right now to support git.  You can read more in the blog post about
that.

(No comment was entered for this change.)

I am voting for this as I would really love to have everything with google and google
not having git means that cannot happen for me.

Me too.
Using git-svn works, but is not very elegant as most of git's branching features and stuff can't be used natively.
Native Git support would be really helpful.

#5: doesn't surprise me that git-svn gives bad results. I'm sure you'll get much 
better results if you use a Git<->Mercurial bridge instead; try it. A DVCS can talk 
to any other DVCS much better than to any centralized VCS.

Google use git for its own project like Android. Why google code can't support git?
It's ridiculous. That's why we Android developers host our code outside google code.
Does that what goole hope to see?

@cwhuang01:  android uses git because that's what the linux kernel uses -- it makes 
sense to follow the linux community.  It's even hosted at kernel.org.

Tell you what... as soon as git can do HTTP reasonably, let us know, and we can look 
into the issue of git on googlecode.  :-)  Meanwhile, mercurial is available on 
googlecode and should give you almost the exact same features.

Having support for Git would be very nice. I understand that supporting all existing
DVCS is out of the question for Google Code, but Git has made it's proofs and is here
to stay. It's no longer the cool fashion of the summer as it has now a large amount
of projects that migrated to it (Linux Kernel, Gnome, Qt, Perl, Debian, Fedora, ...).
It also has a lot of supporters, users, tools and extra web services that provide
sharing capabilities (gitbug, gitorious, etc).

As of today google code has two major version control systems, so joining a public
project is no longer a simple task as one has to know which VCS the project uses. I
think that adding Git to the list of VCS will not bring too much confusion to google
host, it can only bring more projects.

The question now is how many projects would have adopted Git if they would have had
the chance to? And how many projects have left Google Code due to the absence of Git?

Hmm... The "star" button is to vote +1 on an issue; how do I vote -1? :P

-1 from me too,  issue #2674  comment 2

@sussman Git over HTTP is now more efficient as of version 1.6.6. For more 
information see http://progit.org/2010/03/04/smart-http.html. I guess this is now 
something to look into? :)

@rickvug We're very aware of this, since it was a googler who wrote the new HTTP 
protocol.  :-)

(No comment was entered for this change.)

(No comment was entered for this change.)

Now that Eclipse Labs is hosted on Google Code, it's pretty embarrassing to not have 
git support. There is a huge push for git for Eclipse projects. For projects starting 
at the Labs or customizing something at Eclipse, having git support would really help.

Repeating my comment 13 here:  "we're very aware of [git's new http protocol], since it was a googler who wrote 
it".

Sorry for flooding your email a little bit, but just a few thoughts.

Just to make sure that I understand you correctly. The fact that a googler wrote a
git's new http protocol means that google is interested in git hosting and in near or
distant future support here will be added, right?

Or does it mean only that Google is aware and will do it in some abstract future?

Or that Google has a policy to never pre-announce anything and they're trying to tell 
us it's coming without telling us it's coming. I'm happy with that answer.

Yes, that is correct. We do not pre-announce features. We are aware of the current state of Git, but I would not 
read too much into that. 

Now there's an answer which can be taken any number of ways.
I imagine if Google is in it for the long haul(of which I am certain) then git support 
has to be in the pipeline. It's just a question of when, not if...unless Google has 
devilishly more elaborate plans.

Typically, "me-too" comments are unhelpful, as is complaining about how long this has 
been waiting. The issue is marked as an enhancement, and has been reviewed. Unless 
your comments helps with the technical implementation of the requested feature, please 
refrain from sending everyone watching this report an email. Consider starring the 
page instead of leaving a comment that has no significant value.

Hi.

Have started a Git's Smart HTTP (git-http-backend) server implementation as WSGI 
(Python) app.

At this stage (May 26, 2010) it supports pull, push over HTTP with git's Smart HTTP 
RPC.

Authentication is not implemented at all yet, cause it's going to be a separate WSGI 
middleware - independent of git-http-backend "functional" parts.

http://github.com/dvdotsenko/git_http_backend.py

I know that code.google.com runs on Python, so my lib is, at least could be a proof 
of concept for git Smart HTTP potentially coming to code.google.com

(By the way, was a big fan of code.google.com in the earlier days. Love of git turned 
out to be stronger than my appreciation for code.google.com. Hope will be able to 
help google move code.google to Git and return the masses to it.)

Daniel.

there must not be any bias in the opensource community based on the tool being used.

I like git very much. Please support it.

Git support would be a tremendous bonus for me.  Please, please support it.

I love git.

I'm collaborating on an open source project and if Google Code supported git hosting, I'ld push to move the project here for sure!

Hmmm, so now git has "reasonable http support."

Real git support please!

I love git. Please support it.

Seriously support git please!

Stop it! Don't spam my mailbox!

Use the Starbutton left of " Issue 2454 : native git support" to express your love.

Another new GIT fan. I would also like google code to offer a pay for private repository service, like github does.

dave

Have been using git for two years and I still find it knock the socks off any other tools out there. There is no reason google can not support it. It has been chosen as the de facto SCM for open source/free software projects.

I love git

@35: That's a very loaded statement. The Ubuntu community uses Bazaar almost exclusively. The Python community prefers Mercurial. I don't see there being any clear consensus as to which DVCS is the "de facto" choice for the FOSS community. 

@34: So why don't you just use github? It looks like there are plenty of options for Git hosting, and at a glance Github offers you everything Google Code does and more.
https://git.wiki.kernel.org/index.php/GitHosting

@37: c'mon -- while other DVCSs certainly have their fans and their success stories, it's pretty clear that git has quite a bit more momentum and more mindshare than any other DVCS at this point (and that's despite its traditional shortcomings such as windows support, and until recently the lack of a decent http protocol).

I know the google code guys have always seemed generally opposed to adding git support (some of the reason is presumably technical, but I get the feeling that there's more to it than that) -- but really, it's time.

We're listening, we promise.  This is one of the most starred issues in our whole bugtracker.  Google's policy is *not* to officially pre-announce new features or give release dates, so we're not going to say anything about that.  

However:  keep in mind that adding another version control system isn't just a matter of throwing some stuff in /usr/local/bin and handing out ssh accounts;  for both svn and hg, we had to spend a *long* time writing clean-room server implementations that ran on Google's scalable, multi-data-center infrastructure.  This is one of the big things that differentiates Google Code's hosting services:  we need to scale.

@sussman are you saying that git's native code doesn't scale?

git's native code "scales" in the sense that it runs well on a big server. But "scale" means more than that for guys like Google, it needs to scale on a large cluster. 

Git relies on the filesystem to scale, and network filesystems usually do not scale that well. Google stores data in a kind of database called bigtable. See this for how they did it for Mercurial:

http://www.google.com/events/io/2009/sessions/MercurialBigTable.html

See also what the github guys did for Git:

https://github.com/blog/530-how-we-made-github-fast

so no, it's not just a matter of putting the right binary in /usr/local/bin ;-)

(No comment was entered for this change.)

(No comment was entered for this change.)