git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 1/2] fetch: add missing documentation

From
Jeff King <peff@peff.net>
Date
Sep 24, 2013, 05:30 UTC
Message-ID
<20130924053023.GA5875@sigill.intra.peff.net>
In-Reply-To
<CAMP44s1FFTS=wOcWBfqg3zt3TO-aM83oXHcGwBcwvt_HnXrn8g@mail.gmail.com>
On Tue, Sep 24, 2013 at 12:23:21AM -0500, Felipe Contreras wrote:
> > Should this be "upstream remote" rather than "upstream branch"? I don't
> > think we should be looking at branch.*.merge at all for git-fetch.
> 
> As a general user, how do I configure the "upstream remote"?

Yeah, it's not a term we use elsewhere, so it's not great. Probably "default remote" would be better, or even just say "branch.*.remote for the current branch" or something.

I dunno. I don't particularly like any of those, but I really dislike the imprecision of "upstream branch" in this case.

-Peff
Previous: Felipe ContrerasNext: Felipe Contreras
Message 5 of 15 in “fetch: trivial fixes”
  1. 0/2 fetch: trivial fixesFelipe Contreras, Sep 21, 2013
  2. 1/2 fetch: add missing documentationFelipe Contreras, Sep 21, 2013
  3. Jeff KingSep 24, 2013
  4. Felipe ContrerasSep 24, 2013
  5. Jeff KingSep 24, 2013
  6. Felipe ContrerasSep 24, 2013
  7. Jeff KingSep 24, 2013
  8. Felipe ContrerasSep 24, 2013
  9. Jeff KingSep 24, 2013
  10. Felipe ContrerasSep 24, 2013
  11. Jeff KingSep 24, 2013
  12. Felipe ContrerasSep 24, 2013
  13. 2/2 remote: fix trivial memory leakFelipe Contreras, Sep 21, 2013
  14. Jeff KingSep 24, 2013
  15. Junio C HamanoOct 15, 2013

Read the whole thread, see it on lore, or plain text.

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