From: sudipm.mukherjee@gmail.com (Sudip Mukherjee)
To: kernelnewbies@lists.kernelnewbies.org
Subject: doubt with git and linux-next
Date: Mon, 28 Jul 2014 17:57:36 +0530 [thread overview]
Message-ID: <CADVatmPMaHt3BKfsYJuRM1cSj3epSNLiMsDGYXEaQkdMGjKuvg@mail.gmail.com> (raw)
In-Reply-To: <CADVatmM-tOfoH7mZKoadOH9nJbunH39YBqF4Rjvb8XYFL4+xLg@mail.gmail.com>
On Fri, Jul 25, 2014 at 7:55 PM, Sudip Mukherjee
<sudipm.mukherjee@gmail.com> wrote:
> On Fri, Jul 25, 2014 at 7:52 PM, Lucas Tanure <tanure@linux.com> wrote:
>> I had the same issue. I cloned a new one, and every time that I need to
>> update I do those commands, and now I never got the issue again.
>
> Thanks. will check tomorrow if i dont use git pull and only use git
> remote update and git reset --hard master then the issue is coming or
> not.
>
Thanks again. It has worked perfectly . No issues this time .
>>
>> --
>> Lucas Tanure
>> +55 (19) 988176559
>>
>>
>> On Fri, Jul 25, 2014 at 11:14 AM, Sudip Mukherjee
>> <sudipm.mukherjee@gmail.com> wrote:
>>>
>>> On Fri, Jul 25, 2014 at 7:40 PM, Lucas Tanure <tanure@linux.com> wrote:
>>> > Hi,
>>> >
>>> > Could you try:
>>> >
>>> > $ git remote update
>>> > $ git reset --hard origin/master
>>>
>>> then git pull master is not at all a necessary step ??
>>>
>>> I have mentioned in my mail that " then i used : git reset --hard
>>> master , so now git status is showing
>>> "include/linux/mvebu-v7-cpuidle.h" as an untracked file ... "
>>> but i have not modified that file .
>>>
>>>
>>>
>>>
>>> >
>>> > Thanks
>>> >
>>> > --
>>> > Lucas Tanure
>>> > +55 (19) 988176559
>>> >
>>> >
>>> > On Fri, Jul 25, 2014 at 11:06 AM, Sudip Mukherjee
>>> > <sudipm.mukherjee@gmail.com> wrote:
>>> >>
>>> >> Hi,
>>> >> I am having some doubt regarding git and how to sync my local copy
>>> >> with linux-next. I have cloned it and the next day if I want to sync
>>> >> my master with linux-next , i am using :
>>> >> git remote update
>>> >> git pull master
>>> >>
>>> >> Then it is giving some messages about some conflicts. For example If i
>>> >> am trying to sync with todays tree (next-20140725) i got some
>>> >> conflicts. So to merge the conflicts I used
>>> >> git commit -a
>>> >> but then git status is showing "Your branch is ahead of
>>> >> 'master/master' by 271 commits"
>>> >> then i used : git reset --hard master , so now git status is showing
>>> >> "include/linux/mvebu-v7-cpuidle.h" as an untracked file ...
>>> >> Can you anyone please tell me what is the actual and proper way to
>>> >> sync with that days tree ..
>>> >>
>>> >> Thanks in advance
>>> >> Sudip
>>> >>
>>> >> _______________________________________________
>>> >> Kernelnewbies mailing list
>>> >> Kernelnewbies at kernelnewbies.org
>>> >> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>>> >
>>> >
>>
>>
next prev parent reply other threads:[~2014-07-28 12:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 14:06 doubt with git and linux-next Sudip Mukherjee
2014-07-25 14:10 ` Lucas Tanure
2014-07-25 14:14 ` Sudip Mukherjee
2014-07-25 14:22 ` Lucas Tanure
2014-07-25 14:25 ` Sudip Mukherjee
2014-07-28 12:27 ` Sudip Mukherjee [this message]
2014-07-25 17:30 ` Valdis.Kletnieks at vt.edu
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=CADVatmPMaHt3BKfsYJuRM1cSj3epSNLiMsDGYXEaQkdMGjKuvg@mail.gmail.com \
--to=sudipm.mukherjee@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 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).