kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: rpjday@crashcourse.ca (Robert P. J. Day)
To: kernelnewbies@lists.kernelnewbies.org
Subject: working with linux-next ... must tags be fetched separately?
Date: Sun, 28 Jun 2015 05:29:15 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.11.1506280525330.19754@localhost> (raw)


  perusing the current instructions on how to work with linux-next
here:

https://www.kernel.org/doc/man-pages/linux-next.html

and i'm puzzled by this part of the instructions:

 Fetch linux-next plus tags

    $ git fetch linux-next
    ...
    $ git fetch --tags linux-next
    ...

is it really necessary to run two separate fetch commands? from the
man page for git-fetch, one reads:

       -t, --tags
           Fetch all tags from the remote (i.e., fetch remote tags refs/tags/* into local tags with
           the same name), in addition to whatever else would otherwise be fetched.

so would it not be sufficient to run simply:

    $ git fetch --tags linux-next

or am i misreading something?

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

             reply	other threads:[~2015-06-28  9:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-28  9:29 Robert P. J. Day [this message]
2015-06-28  9:38 ` working with linux-next ... must tags be fetched separately? Harsh Jain
2015-06-28  9:42   ` Robert P. J. Day
2015-07-01 23:09     ` Jerry Snitselaar

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=alpine.LFD.2.11.1506280525330.19754@localhost \
    --to=rpjday@crashcourse.ca \
    --cc=kernelnewbies@lists.kernelnewbies.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).