On Wed, 3 Aug 2005, Josef Weidendorfer wrote:
> But my example shows that the error happens even with 2 branches totally
> unrelated to each other: if branch1 got a new commit, you can not push to
> branch2 from another clone.
Sure you can.
git-send-pack remote branch2
and you've just done so.
The shorthand of "no branches listed" expands to _all_ branches, and if
you try to send all branches, then you're trying to update "branch1" with
something you don't have. That's your usage error.
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html