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

Re: [PATCH] fix shell command line in example

From
Joey Hess <joey@kitenet.net>
Date
Dec 23, 2011, 17:33 UTC
Message-ID
<20111223173315.GB23049@gnu.kitenet.net>
In-Reply-To
<8739cbi5v3.fsf@thomas.inf.ethz.ch>
Thomas Rast wrote:
Show 8 quoted lines
>   * Update the upstream origin of the current branch, then merge the
>     tracked branch into the current one:
>   +
>   --------------------------------------------------
>   $ git pull
>   --------------------------------------------------
> 
> modulo avoiding confusion around upstream/tracking.

I support having a simple "git pull" example; I think it's the first thing users should be reaching for, followed perhaps by "git pull foo bar" when they have multiple remotes.

Still, an example of pulling all tracking branches from a remote and merging in the right one for the currently checked out branch would be good to have, that's also a common need when using git without a centralized origin. AFAICS, there's no way to do all that in a single git pull command? My feeling was that this sort of scenario was what the example was trying to do (rather badly).

-- 
see shy jo
Previous: Thomas Rast
Message 3 of 3 in “fix shell command line in example”
  1. fix shell command line in exampleJoey Hess, Dec 23, 2011
  2. Thomas RastDec 23, 2011
  3. Joey HessDec 23, 2011

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.