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

Re: [PATCH 3/3] fetch --all/--multiple: keep all the fetched branch information

From
Michael Lukashov <michael.lukashov@gmail.com>
Date
Feb 24, 2010, 19:54 UTC
Message-ID
<63cde7731002241154o40ad7e6eh26f20017f7854fc3@mail.gmail.com>
In-Reply-To
<7vpr3uqwya.fsf_-_@alter.siamese.dyndns.org>
Patch 3 does not apply correctly:
Applying: fetch --all/--multiple: keep all the fetched branch information
error: patch failed: t/t5521-pull-options.sh:72
error: t/t5521-pull-options.sh: patch does not apply
Patch failed at 0001 fetch --all/--multiple: keep all the fetched
branch information
When you have resolved this problem run "git am --resolved".
If you would prefer to skip this patch, instead run "git am --skip".
To restore the original branch and stop patching run "git am --abort".
On Wed, Feb 24, 2010 at 10:02 PM, Junio C Hamano <gitster@pobox.com> wrote:
Show 5 quoted lines
> Since "git fetch" learned "--all" and "--multiple" options, it has become
> tempting for users to say "git pull --all".  Even though it may fetch from
> remotes that do not need to be fetched from for merging with the current
> branch, it is handy.
>
Previous: Teemu LikonenNext: Junio C Hamano
Message 5 of 7 in “t5521: fix and modernize”
  1. 1/2 t5521: fix and modernizeJunio C Hamano, Feb 24, 2010
  2. 2/2 builtin-fetch --all/--multi: propagate options correctlyJunio C Hamano, Feb 24, 2010
  3. 3/3 fetch --all/--multiple: keep all the fetched branch informationJunio C Hamano, Feb 24, 2010
  4. Teemu LikonenFeb 24, 2010
  5. Michael LukashovFeb 24, 2010
  6. Junio C HamanoFeb 24, 2010
  7. Michael LukashovFeb 24, 2010

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.