git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Sanderson <yelliott@gmail.com>
To: git@vger.kernel.org
Subject: git pull --prune --prune-tags yields a usage error In 2.45.0
Date: Mon, 13 May 2024 19:11:00 -0400	[thread overview]
Message-ID: <CAC-6ESEfnjK1ubrzoAfUsegM55e55uKugCPSfxnBC607dmZJRA@mail.gmail.com> (raw)

I noticed that "git help pull"  mentioned the flag --prune-tags in
conjunction with --prune, but actually supplying this flag to
"git pull" results in a usage error.  For instance, the command
"git pull --prune --prune-tags" fails with a usage error.  I would
have expected that this would work, since it works with "git fetch".

I could use "git fetch --prune --prune-tags" as I expected, and
"git help fetch" does describe --prune-tags on its own as well as
in the help for --prune.

I confirmed that this behavior still exists in git version 2.45.0.

David Sanderson

             reply	other threads:[~2024-05-13 23:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-13 23:11 David Sanderson [this message]
2024-05-14  6:47 ` git pull --prune --prune-tags yields a usage error In 2.45.0 Patrick Steinhardt

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=CAC-6ESEfnjK1ubrzoAfUsegM55e55uKugCPSfxnBC607dmZJRA@mail.gmail.com \
    --to=yelliott@gmail.com \
    --cc=git@vger.kernel.org \
    /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).