kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: dev@snitselaar.org (Jerry Snitselaar)
To: kernelnewbies@lists.kernelnewbies.org
Subject: working with linux-next ... must tags be fetched separately?
Date: Wed, 1 Jul 2015 16:09:07 -0700	[thread overview]
Message-ID: <20150701230907.GB2357@rhwork.redhat.com> (raw)
In-Reply-To: <alpine.LFD.2.11.1506280541460.20040@localhost>

On Sun Jun 28 15, Robert P. J. Day wrote:
> On Sun, 28 Jun 2015, Harsh Jain wrote:
> 
> > Hi,
> >
> > git fetch --tags linux-next
> >
> > Will only fetch the tags not changed files content/data.
> >
> > To fetch file changes
> > git fetch linux-next
> >
> > Is required.
> >
> >
> >
> > On 28 June 2015 14:59:15 GMT+05:30, "Robert P. J. Day" <rpjday@crashcourse.ca> wrote:
> >
> >   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
> 
>   that suggests that the man page is slightly misleading, given that
> it clearly states that "--tags" will fetch tags, "in addition to
> whatever else would otherwise be fetched." or is there a different way
> to read that phrase?
> 
> rday
> 

It seems to work as described in the manpage for me:

snits at cantor:~/dev/linux=>git fetch -t linus
remote: Counting objects: 888, done.
remote: Compressing objects: 100% (158/158), done.
remote: Total 888 (delta 798), reused 818 (delta 730)
Receiving objects: 100% (888/888), 137.18 KiB | 0 bytes/s, done.
Resolving deltas: 100% (798/798), completed with 368 local objects.
>From git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux
   0890a26..6ac15ba  master     -> linus/master
snits at cantor:~/dev/linux=>git --version
git version 2.4.3.368.g7974889

      reply	other threads:[~2015-07-01 23:09 UTC|newest]

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

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=20150701230907.GB2357@rhwork.redhat.com \
    --to=dev@snitselaar.org \
    --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).