From: yuzibode@126.com (YU Bo)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Merge conflict
Date: Mon, 15 Feb 2016 22:16:48 +0800 (CST) [thread overview]
Message-ID: <253e29fa.3c04.152e54a762a.Coremail.yuzibode@126.com> (raw)
In-Reply-To: <CADuXt-XGQkzhV7EUUx7TAB9hyFfKN+ir9Hs2Fr6iVM5eLD0Yxw@mail.gmail.com>
Hello,
At 2016-02-15 16:57:46, "Ebru Akag?nd?z" <ebru.akagunduz@gmail.com> wrote:
>Hello,
>
>>> Hi,
>>> Some days ago i followed the tips:
>>> http://kernelnewbies.org/FirstKernelPatch
>>> git clone greg's git tree and built branch first-patch.
>>> Due to my first patch that fixes coding style reported
>>> by checkptch.pl didn't applied,so i intend to rebase my
>>> git branch first-patch.The question i encounter is:
>>> ==================git command && output========
>>> yubo at debian:~/maintree/staging$ git rebase first-patch
>>> It looks like git-am is in progress. Cannot rebase.
>>> yubo at debian:~/maintree/staging$ git am --abort
>>> You seem to have moved HEAD since the last 'am' failure.
>>> Not rewinding to ORIG_HEAD
>>> yubo at debian:~/maintree/staging$ git rebase first-patch
>>> First, rewinding head to replay your work on top of it...
>>> Applying: ovl: default permissions
>>> Using index info to reconstruct a base tree...
>>> Falling back to patching base and 3-way merge...
>>> ----
>>> Auto-merging drivers/gpu/drm/i915/intel_display.c
>>> CONFLICT (content): Merge conflict in drivers/gpu/drm/i915/intel_display.c
>>> Failed to merge in the changes.
>>> Patch failed at 0010 drm/i915: Only run commit when crtc is active, v2.
>>>
>>> Is there something with wrong?
>>> Thanks in advance for the noisy.
>
>If you would like to update your patch with newest version of the tree,
>I recommend to you, use git am. Here is the blog post:
>http://www.pizzhacks.com/bugdrome/2011/10/deal-with-git-am-failures/
>
>After updating your current tree;
>
>Firstly, you should give the command:
>1- git am your_old_patch
>
>After seeing, it could not be applied, give this:
>2- git apply PATCH --reject
>
>You'll see rejected and applied chunks, the rejected parts will be specified
>with extension .rej (with related file name). You should edit related
>files manually.
>
>3- git add fixed_files
>4- git am --resolved
>
>
>All done :). This way seems easier to me. The blog post explained
>steps, quite clear as well.
>
Thanks. I will learn more about git.
>Kind regards,
>Ebru
>
>--
>Ebru Akagunduz
>http://www.ebruakagunduz.com
>
>_______________________________________________
>Kernelnewbies mailing list
>Kernelnewbies at kernelnewbies.org
>http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20160215/2a824b4c/attachment.html
prev parent reply other threads:[~2016-02-15 14:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-14 23:46 Merge conflict YU Bo
2016-02-14 23:51 ` Roger H Newell
2016-02-15 0:10 ` YU Bo
2016-02-15 0:15 ` YU Bo
2016-02-15 8:57 ` Ebru Akagündüz
2016-02-15 14:16 ` YU Bo [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=253e29fa.3c04.152e54a762a.Coremail.yuzibode@126.com \
--to=yuzibode@126.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).