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

Re: [PATCH v2] Documentation/git-pull: clarify configuration

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Nov 11, 2010, 08:31 UTC
Message-ID
<20101111083124.GB15525@burratino>
In-Reply-To
<AANLkTikT4N5JAxRxPCbx=xAokRKOvvxDQ4pAC9CcpObB@mail.gmail.com>
Martin von Zweigbergk wrote:
Show 6 quoted lines
>                                           I happened to spot a similar
> problem in the documentation for 'git rebase -s'. It currently says "Use
> the given merge strategy. If there is no -s option git merge-recursive
> is used instead. This implies --merge." and I assume the last sentence
> refers to the first one in this case too. Same question here: Should I
> send a patch?
Yes, please!

In general, carefully written patches that improve the documentation are always welcome. (And sloppy patches are not so bad, either.)

Previous: Martin von Zweigbergk
Message 6 of 6 in “Documentation/git-pull: clarify configuration”
  1. Documentation/git-pull: clarify configurationMartin von Zweigbergk, Nov 10, 2010
  2. Jonathan NiederNov 10, 2010
  3. Martin von ZweigbergkNov 11, 2010
  4. Junio C HamanoNov 10, 2010
  5. Martin von ZweigbergkNov 11, 2010
  6. Jonathan NiederNov 11, 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.