Re: push.default: current vs upstream

From: Jeff King <peff@peff.net>
Date: Apr 12, 2012, 07:11 UTC
Message-ID: <20120412071150.GB31122@sigill.intra.peff.net>
In-Reply-To: <4F7FFD7A.80104@pileofstuff.org>

On Sat, Apr 07, 2012 at 09:40:26AM +0100, Andrew Sayers wrote:

Show 5 quoted lines

> On a slight aside, should we add @{downstream} to describe the opposite
> of @{upstream}?  Seeing that around the place would give intermediate
> users a clue about why pull and push aren't as related as they think,
> and would be useful here and there in code (e.g. __git_ps1 could show a
> better bash prompt with GIT_PS1_SHOWUPSTREAM).

Maybe. I don't really see how it is useful, but maybe you want to flesh our your proposal with some examples? I do not use __git_ps1, so I'm not sure what you want to improve there.

-Peff

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.