7 ms·
V8 Moving to Git
- TheAceOfHearts 12y agoI'm curious if they'll be moving to GitHub as well. It seems that would be another nail in Google Code's coffin.
- TheHydroImpulse 12y agoI don't know about them moving to Github, but the v8/v8 repo [0] (currently the svn mirror) has been deprecated and the git repo mirror will replace it in the near future [1]. That's the extend of them using Github as far as I know. [0]: https://github.com/v8/v8 https://github.com/v8/v8 [1]: https://groups.google.com/forum/#!topic/v8-users/VgL3Fn4ijqE https://groups.google.com/forum/#!topic/v8-users/VgL3Fn4ijqE
- mraleph 12y agoNo. V8 has moved to Chromium's Git infrastructure, not GitHub. https://chromium.googlesource.com/v8/v8.git https://chromium.googlesource.com/v8/v8.git
- baldfat 12y agohttps://github.com/v8/v8-git-mirror https://github.com/v8/v8-git-mirror
- baldfat 12y agoIt is good to see that a company can accept that there is a better tool, github. I remember when I thought sourceforge was so good. Now I silently weep when I need to go there for anything.
- bigtones 12y agoGit is not Github. They are moving to Git but it's hosted on Google, not Github.
- xxgreg 12y agoAnd since git is distributed it can be hosted on both, and already is https://github.com/v8/v8-git-mirror https://github.com/v8/v8-git-mirror
- bbcbasic 12y agoWhat is the advantage of having a mirror? Aren't mirrors going to be slightly out of date (unless continually synchronised). And you wouldn't commit to the mirror, right?
- adrianm 12y agoI can't speak for everyone, but I appreciate the mirrors because I enjoy reading and searching through codebases on Github, so having the repository mirrored there is useful.
- akoeplinger 12y agoIf you look below the repository title on GitHub, it says "mirrored from..". This means GitHub handles the synchronization (they set this up on request for some projects). For me the advantage is being able to use GitHub's nice UI to browse the source code.
- xxgreg 12y agoGithub has some nice features that chromium.googlesource.com lacks, like being able to list all of the commits that have changed files in a specific sub directory. Synchronising a mirror automatically is pretty trivial so I imagine they're usually pretty up to date.
- tn13 12y agoThis is good. Github mirrors of the repo are already available. Even though this does not help contributors it would help people like me to play with v8 lot more.
- Bahamut 12y agoI thought V8 has been in the process of moving to git for a little while? It has some weird git/svn hybrid setup currently I believe.
- amelius 12y agoI hope they also modify their build process a little. Right now, when you want to build V8, it automatically downloads all the tools it depends on. This makes it difficult to store one particular version of the library and all the tools it depends on.
- JoshTriplett 12y agoI look forward to seeing the rest of Chromium follow. Hopefully it'll move from Reitveld to Gerrit and repo in the process. Reitveld has SVN support, but it and its command-line tools are otherwise more painful than Gerrit in every way.
- magicalist 12y agoMaybe I'm misunderstanding you, but Chromium migrated to git in August: https://groups.google.com/a/chromium.org/d/msg/chromium-dev/7WFImJ8Y1V0/jmSiaxggx4AJ https://groups.google.com/a/chromium.org/d/msg/chromium-dev/...
- JoshTriplett 12y agoIt's been a long transition; as far as I can know, Chromium is still using gclient, git cl, and reitveld, rather than repo and Gerrit.
- deleted 12y ago[deleted]
- deleted 12y ago[deleted]
- cenhyperion 12y agoIf you're still using Google Code for any projects I'd really recommend moving it to another service at this point unless you have a compelling reason to stay. There's some good evidence at this point that's leading me to believe Google Code is next on the chopping block for dead Google services.
- ghostdiver 12y agoSorry, but I really like Google Code source browser with its awesome features like searching for definitions, instantiations, calls, declarations etc. GitHub is very poor on that matter.
- moab 12y agoHe wasn't saying google code was bad, just that it's likely the next service to be cut by our friends over at Google. Given that v8's moving, this is pretty reasonable prediction.
- deleted 12y ago[deleted]
- Drakim 12y agoThat won't matter if Google Code disappears, none of those features will work then. That's what he is warning against.
- 10098 12y agoThey're not moving to github though, just switching VCS.
- Aldo_MX 12y agoAlthough Google has earned a bad reputation by shutting down some of their services, I think this recommendation is simply FUD. 1. v8 is just a Google project. Their decisions doesn't represent the company as a whole. 2. They just changed the VCS. 3. When Google is going to shut down a service, they warn you several months in advance. Honestly, whether Google will shut down Google Code or not should not be a concern until they announce it officially...
- baldfat 12y agoI got 4 down votes them saying: "Git doesn't equal github" My post: It is good to see that a company can accept that there is a better tool, github. They were WRONG Google is moving to github https://github.com/google https://github.com/google Lots of repos are hours old thanks down voters.
- TheHydroImpulse 12y agoGoogle has had a Github account for a long time now. That doesn't mean they're moving all development over to Github for all Google projects. And the v8 project is moving to Google's Git infrastructure, not Github.
- Bahamut 12y agoYou do know that Google has had a presence on GitHub for quite a while. AngularJS, Polymer, CCA, Dart, Go, Karma...I'm sure there are many other examples.
- random_ind_dude 12y agoThe commit message "Fix mozilla expectations after regexp change" looked interesting to me and I took a look at the change. https://chromium.googlesource.com/v8/v8.git/+/5d65e1374fd9c5f7e1981bb28f234eaa0a309082 https://chromium.googlesource.com/v8/v8.git/+/5d65e1374fd9c5... Looks like V8 runs Mozilla's JS tests too. I didn't know that. Does Mozilla do something similar to ensure that V8's tests work in Mozilla(Firefox) as well?
- gsnedders 12y agoMozilla's JS tests have for a while been run by everyone else because they have typically tested a lot of de-facto required behaviour that isn't specified anywhere. That said, the problem with both them and mjsunit (V8's JS testsuite) is they freely mix tests for unimportant implementation detail (say, details of enumeration order!) and what is de-facto required. In the end, with Carakan, we decided it wasn't worth the time to get the mjsunit tests running — they found almost nothing that weren't found otherwise — and coming up with proper expectations and keeping them up to date does take time.
- deleted 12y ago[deleted]
- Osiris 12y agoI find it interesting that they commit directly to master. I didn't see any branch merges at all. What is their workflow if they don't use branches? Do developers work offline on a fix then squash all their changes into a single commit and push it to master? Generally having so many devs working off the same branch at the same time can be a bit problematic. My philosophy is that master should be for branch merges only.
- badgersandjam 12y agoYou never know with git. Which is one of my big problems with it. The picture on master doesn't necessarily represent what happens on other repos across your organisation.
- phaemon 12y agoI don't understand the problem. Which VCS does tell you what your developers are doing on their machines before they commit to your main repository?
- badgersandjam 12y agoNone. However svn prevents them doing anything major unless they tell someone.
- phaemon 12y agoYou mean like Gerrit? Or do you mean something else?
- qznc 12y agoJust do fast-forward merges. This means before pushing into the central repo, you rebase your feature branch onto origin/master. Cleaner history and easier to bisect. However, I prefer non-fast-forward merges for features branches which break in between. Although rebase on origin/master is still good, because you find merge-bugs locally.