Re: {Spam?} push pull not working

From: Junio C Hamano <gitster@pobox.com>
Date: Jan 24, 2012, 20:28 UTC
Message-ID: <7vliow3kx8.fsf@alter.siamese.dyndns.org>
In-Reply-To: <20120124201807.GA20145@sigill.intra.peff.net>

Jeff King <peff@peff.net> writes:

Show 13 quoted lines

> 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.