From: adr3nald0s@gmail.com
To: git@vger.kernel.org
Subject: Anomalous conflicts during git rebase
Date: Thu, 27 Dec 2007 16:42:57 -0600 [thread overview]
Message-ID: <m3ir2ju5ce.fsf@euroclydon.lan> (raw)
On a clone of linux-2.6:
git checkout -b topic/test v2.6.15
touch drivers/a-file.c
git add drivers/a-file.c
git commit -m 'Add a file'
git checkout -b temp0 v2.6.16
git rebase topic/test
I get the following:
Applying [ACPI] handle ACPICA 20050916's acpi_resource.type rename
error: patch failed: drivers/acpi/glue.c:99
error: drivers/acpi/glue.c: patch does not apply
error: patch failed: drivers/char/hpet.c:897
error: drivers/char/hpet.c: patch does not apply
Using index info to reconstruct a base tree...
Falling back to patching base and 3-way merge...
Auto-merged drivers/acpi/glue.c
Auto-merged drivers/acpi/pci_link.c
Auto-merged drivers/char/hpet.c
CONFLICT (content): Merge conflict in drivers/char/hpet.c
Failed to merge in the changes.
Patch failed at 0007.
When you have resolved this problem run "git rebase --continue".
If you would prefer to skip this patch, instead run "git rebase --skip".
To restore the original branch and stop rebasing run "git rebase --abort".
Is this a bug, or is there a reason I am seeing conflicts in files
I've never touched?
next reply other threads:[~2007-12-27 22:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-27 22:42 adr3nald0s [this message]
2007-12-27 22:57 ` Anomalous conflicts during git rebase Johannes Sixt
2007-12-28 15:35 ` adr3nald0s
2007-12-27 23:45 ` Daniel Barkalow
2007-12-28 15:54 ` adr3nald0s
2007-12-28 17:58 ` Daniel Barkalow
2007-12-28 18:33 ` adr3nald0s
2007-12-28 18:54 ` Björn Steinbrink
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=m3ir2ju5ce.fsf@euroclydon.lan \
--to=adr3nald0s@gmail.com \
--cc=git@vger.kernel.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.