Jeff King <peff@xxxxxxxx> writes: > This might have been a better example (it exhibits the problem, but is > not an example of a terrible thing to be doing): > > 1. repo1 has a "master" branch > > 2. clone repo1 with "git clone --bare repo1 repo2". Repo2 now has a > master branch. > > 3. create a new "foo" branch in repo and commit on it > > 4. "git push ../repo2" from repo1. This is a sane thing to be doing, > but will not push the newly-created "foo" branch, as some users > might expect. Yeah, that is pretty much the standard thing people would do, at least before GitHub era ;-), to start a project in repo1, and then to publish for others to fetch at repo2. Thanks for clarification. P.S. Did you have chance to take a look at the "grep" thing? I thought "grep --textconv" would make sense, but I may be missing some large pitfalls. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html