Adam Bliss

> > > I agree that working completely in git-meta and not at the submodule would > be ideal. However, the reality is that we will not be able to...

Would it suffice if `git meta push origin HEAD:refs/heads/foo` would attempt to push each changed submodule to `refs/heads/foo` in its own remote? That should be pretty easy to implement, and...

Ok, I updated the title to reflect the new goal. I propose the config be named `gitmeta.pushSubmoduleBranches` and I think it should probably be just a couple-line change around https://github.com/twosigma/git-meta/blob/master/node/lib/util/push.js#L230...

Yeah, I guess the default should be something like: 1. (optional, but probably a good idea): fetch all repos that you plan to push, and check that each push is...

One could argue that "git log" should do this, and that its current behavior is broken (it seems to list any commits touching the submodule prefix, regardless of which files...

Not according to "git status".

I just saw a variant: ``` abliss@home:~/src/metaqa2$ git meta checkout 6f42cf51174561e037dc09e64000597e36dc4ace Unable to checkout submodule ts/foo/bar: 1 conflict prevents checkout. ``` When I instead do a `git checkout` and a...

Actually, now that I think about it, why include document polls in the ETH layer at all? Couldn't it be implemented in 5 lines of Hoon, rather than 60+ lines...

Yes, the issue appears to be in the way `pyficache` calls `coverage`.. I'm trying to figure out if there's a config that can be set in `trepan3k` to avoid the...

Thanks for the quick response! I force-pushed to fix the lint errors and to add the sign-off-by header. Any chance you could link me directly to the spec's recommendations for...