News for hackers. Stuff that matters.
Re:Why your company shouldn't use Git submodules by exDM69 on Sunday April 29, 2012 @04:11AM (#3905475)
I've said this before but I'll say it again. Stay the hell away from Google's Repo tool. It's a half-baked badly maintained piece of ad-hoc software. It will completely destroy your git workflow. You'll also be married to the crappy review tool called Gerrit.

Repo was made prior to Git submodules to do the exact same thing for Android. Now that Git has submodule support, Repo is useless. It does pretty much the same thing as submodules, but it does it in a very crappy way.

For example, you cannot go back to a specific set of versions of subdirectories with Repo. In other words there's no "global" git bisect as there would be with submodules. This stops you from automatically finding a problem in one of the submodule repos if there are dependencies betweeen the problematic repo and other repositories.

Re:Why your company shouldn't use Git submodules by valley_guy_12 on Sunday April 29, 2012 @09:40AM (#3905944)
Repo seems to work the way it does on purpose:

"...the reason we made repo was because we didn't want to deal with commits in the super project, or trying to merge concurrent branches in the super project. Instead we wanted each subproject to use a floating branch as the revision it is tracking."

https://groups.google.com/d/msg/repo-discuss/ZpqOOE5mLXo/Sw0...

Re:Why your company shouldn't use Git submodules by exDM69 on Sunday April 29, 2012 @10:02AM (#3905983)
If you ask me, it was the wrong choice. I work on a huge project that's hosted on Repo (full Android OS + big proprietary driver tree), and the lack of this feature has really cost me lots of time doing manual labor that could be automated.

Another decision the Repo designers made that I disagree with is the silly Change-Id added to every commit message(!). Since when do globally unique identifiers (GUIDs) solve problems instead of creating more?

Re:Why your company shouldn't use Git submodules by duskwuff on Sunday April 29, 2012 @10:54PM (#3907841)
That's an artifact of Gerrit, not Repo.
Re:Why your company shouldn't use Git submodules by mindjiver on Sunday April 29, 2012 @09:58AM (#3905972)
Well, since the maintainer of repo wants to kill it off, it is perhaps not surprising that it is badly maintained at the moment.
Re:Why your company shouldn't use Git submodules by exDM69 on Sunday April 29, 2012 @10:04AM (#3905991)
Do you have a source for that? If this information is true, I could use it to help convince our management at work that we should move off Repo and into Git submodules.
Re:Why your company shouldn't use Git submodules by mindjiver on Sunday April 29, 2012 @10:38AM (#3906058)
Not on paper but Shawn Pearce (Gerrit/repo maintainer) said it at GitTogether 2011. But wanting to kill something off and actually doing it, they are of course different.

Also, if you do use Gerrit (even though you don't seem to like it) it has some better support for submodules from 2.3 onwards. See https://gerrit-review.googlesource.com/Documentation/user-su...