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

Re: Summary of the problems with git pull

From
DRDamien Robert <damien.olivier.robert+gmane@gmail.com>
Date
May 6, 2014, 20:03 UTC
Message-ID
<lkbf63$p8l$1@ger.gmane.org>
In-Reply-To
<5366db742d494_18f9e4b308aa@nysa.notmuch>

Felipe Contreras wrote in message <5366db742d494_18f9e4b308aa@nysa.notmuch>:

Show 5 quoted lines
> == git update ==
> 
> Another proposed solution is to have a new command: `git update`. This
> command would be similar to `git pull --ff-only` by default, but it
> could be configured to do merges instead, and when doing so in reverse.
Thanks for the nice summary.

As a user, I am very much in favor of adding a `git update` command. In fact I already have a ruby script that does such a thing (fast-forward all my local branches that have an upstream configured), so it would be nice to have it directly in git core.

Previous: Felipe ContrerasNext: Ping Yin
Message 2 of 6 in “Summary of the problems with git pull”
  1. Felipe ContrerasMay 5, 2014
  2. Damien RobertMay 6, 2014
  3. Ping YinMay 7, 2014
  4. Felipe ContrerasMay 10, 2014
  5. Philippe VaucherMay 28, 2014
  6. Felipe ContrerasMay 28, 2014

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.