From: Valdis.Kletnieks@vt.edu (Valdis.Kletnieks at vt.edu)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Problems with Linux next tree
Date: Mon, 14 Jul 2014 17:54:06 -0400 [thread overview]
Message-ID: <36966.1405374846@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Mon, 14 Jul 2014 17:57:10 -0300." <CAJyon0vZMwh2pEnBg_4pCpOsyrffgoA7kvN+RESYNaDcySSQiQ@mail.gmail.com>
On Mon, 14 Jul 2014 17:57:10 -0300, Lucas Tanure said:
> Hi,
>
> No I didn't. It is a clean linux-next tree.
> Turns out that if I don't update every day I got this issue.
Due to the way the linux-next tree is built, 'git pull' won't work.
You want to 'git clone' Linus's master tree, then 'git remote add'
the Linux-next tree. Then use 'git remote update' instead of 'git pull'
when you want to refresh the tree.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 848 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20140714/3435ca99/attachment.bin
next prev parent reply other threads:[~2014-07-14 21:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-14 20:07 Problems with Linux next tree Lucas Tanure
2014-07-14 20:26 ` Prabhakar Lad
2014-07-14 20:57 ` Lucas Tanure
2014-07-14 21:54 ` Valdis.Kletnieks at vt.edu [this message]
2014-07-15 7:45 ` Prabhakar Lad
2014-07-14 20:57 ` Benedict Börger
2014-07-14 21:04 ` Lucas Tanure
2014-07-14 21:18 ` Peter Senna Tschudin
2014-07-14 21:29 ` Lucas Tanure
2014-07-15 6:46 ` Alexey Tulia
-- strict thread matches above, loose matches on Subject: below --
2014-07-15 4:52 黄钦佳
2014-07-15 5:37 ` Stone Kang
2014-07-15 7:47 ` Prabhakar Lad
2014-07-15 14:52 ` Kinka Huang
2014-07-14 19:58 Lucas Tanure
2014-07-15 13:16 ` Varka Bhadram
2014-07-15 13:32 ` Lucas Tanure
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=36966.1405374846@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--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).