git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Elijah Newren via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Elijah Newren <newren@gmail.com>
Subject: [PATCH 0/2] A few --shallow-exclude fixes
Date: Mon, 04 Nov 2024 19:02:42 +0000	[thread overview]
Message-ID: <pull.1822.git.1730746964.gitgitgadget@gmail.com> (raw)

Here's a couple patches to fix up an error message and the documentation
around the --shallow-exclude option.

Elijah Newren (2):
  upload-pack: fix ambiguous error message
  doc: correct misleading descriptions for --shallow-exclude

 Documentation/fetch-options.txt  | 2 +-
 Documentation/git-clone.txt      | 2 +-
 Documentation/git-fetch-pack.txt | 2 +-
 builtin/clone.c                  | 2 +-
 builtin/fetch.c                  | 4 ++--
 builtin/pull.c                   | 4 ++--
 t/t5500-fetch-pack.sh            | 7 +++++++
 upload-pack.c                    | 6 +++++-
 8 files changed, 20 insertions(+), 9 deletions(-)


base-commit: 8f8d6eee531b3fa1a8ef14f169b0cb5035f7a772
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-1822%2Fnewren%2Fshallow-exclude-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-1822/newren/shallow-exclude-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/1822
-- 
gitgitgadget

             reply	other threads:[~2024-11-04 19:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-04 19:02 Elijah Newren via GitGitGadget [this message]
2024-11-04 19:02 ` [PATCH 1/2] upload-pack: fix ambiguous error message Elijah Newren via GitGitGadget
2024-11-05  6:27   ` Patrick Steinhardt
2024-11-04 19:02 ` [PATCH 2/2] doc: correct misleading descriptions for --shallow-exclude Elijah Newren via GitGitGadget
2024-11-05  6:27   ` Patrick Steinhardt
2024-11-05  6:55     ` Junio C Hamano
2024-11-05  1:27 ` [PATCH 0/2] A few --shallow-exclude fixes Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=pull.1822.git.1730746964.gitgitgadget@gmail.com \
    --to=gitgitgadget@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=newren@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).