Git development
 help / color / mirror / Atom feed
From: Tony Luck <tony.luck@gmail.com>
To: git@vger.kernel.org
Subject: git fetch --tags doesn't quite do what I expect
Date: Fri, 18 Nov 2005 11:14:16 -0800	[thread overview]
Message-ID: <12c511ca0511181114jf4ca3c0p195a128fa541b8f2@mail.gmail.com> (raw)

I've been doing some updating on my git scripts to make use of the features
that you have been working hard to put in (thank you).  My script to update
my local "linus" branch from Linus' master branch at kernel.org had a simple
"git fetch linus" (with the appropriate[1] URL and Pull lines in
.git/refs/remotes/linus)
followed by an unholy piece of script that parsed the output from
"git-ls-remote --tags linus" to see if I had all the latest tags, and
get them if
I didn't.

Looking at the manual, I thought that I could just change the "git
fetch linus" to
be "git fetch --tags linus" and drop the script.  But it appears that
with the "--tags"
argument the "fetch" will not fetch anything beyond the tagged commits (i.e.
at the moment v2.6.15-rc1) ... so I need both:
      git fetch --tags linus
and
      git fetch linus

one to get any new tags, and the other to fetch all the way up to "master".

Is this intended behaivour?  If so, the "--tags" entry on the git-fetch(1) man
page needs a little extra text to say that --tags limits the fetch to only
commits reachable from the tags.


-Tony

[1] Contents:
URL: master.kernel.org:/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
Pull: master:linus

             reply	other threads:[~2005-11-18 19:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-18 19:14 Tony Luck [this message]
2005-11-18 20:06 ` git fetch --tags doesn't quite do what I expect Junio C Hamano
2005-11-18 22:04   ` Luck, Tony

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=12c511ca0511181114jf4ca3c0p195a128fa541b8f2@mail.gmail.com \
    --to=tony.luck@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