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

RE: Default behavior of git pull

From
Felipe Contreras <felipe.contreras@gmail.com>
Date
Jul 14, 2021, 15:31 UTC
Message-ID
<60ef0352705ca_261120866@natae.notmuch>
In-Reply-To
<7a97ac78-f405-2dca-2998-f03637cc8255@gmail.com>
Hi Mathias,
I hadn't seen this mail.
Mathias Kunter wrote:
> Wouldn't it make sense if "git pull" would by default also pull the 
> branch with the same name from the remote, in case no upstream is 
> configured?
I agree.

In fact, back in 2014 I wrote a builtin called `git update` to fix all the problems with `git pull`. That command worked exactly as you suggest.

I recently sent a new proposal for `git update` [1] asking for feedback on how different arguments should be handled. Nobody has suggested anything.

For the next iteration I will implement what you suggested, in my opinion it makes sense.

Cheers.
[1] https://lore.kernel.org/git/20210705123209.1808663-1-felipe.contreras@gmail.com/
-- 
Felipe Contreras
Previous: Mathias Kunter
Message 4 of 4 in “Default behavior of git pull”
  1. Mathias KunterMay 31, 2021
  2. Bagas SanjayaMay 31, 2021
  3. Mathias KunterMay 31, 2021
  4. Felipe ContrerasJul 14, 2021

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.