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

Re: [PATCH] doc: sparse-checkout: fix mismatched sq

From
Elijah Newren <newren@gmail.com>
Date
May 21, 2020, 06:14 UTC
Message-ID
<CABPp-BG30_bxNwFWNMMEJDbCrExOaAs5vvaGcydLB1gMxSHXzw@mail.gmail.com>
In-Reply-To
<pull.641.git.1590041164665.gitgitgadget@gmail.com>

On Wed, May 20, 2020 at 11:06 PM starlord via GitGitGadget <gitgitgadget@gmail.com> wrote:

Show 29 quoted lines
>
> From: "bojun.cbj" <bojun.cbj@alibaba-inc.com>
>
> Signed-off-by: bojun.cbj <bojun.cbj@alibaba-inc.com>
> ---
>     doc: sparse-checkout: fix mismatched sq
>
> Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-641%2FBerger7%2Fmaster-v1
> Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-641/Berger7/master-v1
> Pull-Request: https://github.com/gitgitgadget/git/pull/641
>
>  Documentation/git-sparse-checkout.txt | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/git-sparse-checkout.txt b/Documentation/git-sparse-checkout.txt
> index 1a3ace60820..7c8943af7af 100644
> --- a/Documentation/git-sparse-checkout.txt
> +++ b/Documentation/git-sparse-checkout.txt
> @@ -70,7 +70,7 @@ C-style quoted strings.
>         `core.sparseCheckoutCone` is enabled, the given patterns are interpreted
>         as directory names as in the 'set' subcommand.
>
> -'reapply::
> +'reapply'::
>         Reapply the sparsity pattern rules to paths in the working tree.
>         Commands like merge or rebase can materialize paths to do their
>         work (e.g. in order to show you a conflict), and other
>
> base-commit: 87680d32efb6d14f162e54ad3bda4e3d6c908559

Thanks for the patch! It turns out that this one was already submitted by Martin Ågren over here: https://lore.kernel.org/git/69faf4d317547143f455321c5a70575cb7b0b0ad.1589739920.git.martin.agren@gmail.com/

Glad you all are fixing up my mistakes.  :-)
Previous: starlord via GitGitGadget
Message 2 of 2 in “doc: sparse-checkout: fix mismatched sq”
  1. doc: sparse-checkout: fix mismatched sqstarlord via GitGitGadget, May 21, 2020
  2. Elijah NewrenMay 21, 2020

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.