Andrew Sayers <andrew-git@xxxxxxxxxxxxxxx> writes:
> So if the problem is that the documentation cues the reader to think
> about upstreams but not to think about downstreams, the solution is to
> find excuses to talk more about downstreams. As far as I'm concerned
> @{upstream} means "the place that commits come from when I `git pull`",
> so it makes perfect sense to me that @{downstream} would mean "the place
> commits go to when I `git push`".
In a separate message I completely misunderstood what you meant by
"downstream".
If you had something like this:
[remote "origin"]
url = ...
[remote "destination"]
pushURL = ...
[branch "topic"]
remote = origin
merge = refs/heads/master
pushRemote = destination # new
push = refs/heads/topic # new
you could express that asymmetric layout in a natural way. When you say
"git push" while on your "topic" branch, it will go to "destination"
remote to update their "topic" branch.
Interesting...
--
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