From: alexey.tulia@gmail.com (Alexey Tulia)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Problems with Linux next tree
Date: Tue, 15 Jul 2014 09:46:52 +0300 [thread overview]
Message-ID: <53C4CE5C.8070006@gmail.com> (raw)
In-Reply-To: <CAJyon0tXGdhe-Q7b37LPjHw_gPqsD75bKZ6g5XztumCvGUhKyQ@mail.gmail.com>
Hi Lucas,
To follow changes to the linux-tree tree you need to first do a remote
update (this will get all the changes from the remote linux-next branch
to the local origin/master tracking branch) and then reset the HEAD
pointer of current checked out branch to the HEAD of linux-next remote
tracking branch (i.e origin/master).
$ git remote update
$ git reset --hard origin/master
This will make your current branch (master) *exactly* like the remote
linux-next tree. You cannot do pull or merge from the remote tracking
branch.
--
Alexey Tulia
On 07/14/2014 11:07 PM, Lucas Tanure wrote:
> Hi,
>
> My local clone of linux-tree always fails to update.
> When I run git pull origin master, I got a :
> Automatic merge failed; fix conflicts and then commit the result.
>
> So, How I can keep my local tree updated ? No matter what.
>
> Thanks
>
> --
> Lucas Tanure
> +55 (19) 988176559
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
next prev parent reply other threads:[~2014-07-15 6:46 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
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 [this message]
-- 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=53C4CE5C.8070006@gmail.com \
--to=alexey.tulia@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.