From: Len Brown <len.brown@intel.com>
To: git@vger.kernel.org
Subject: Re: needs merge
Date: Sat, 7 Jan 2006 03:57:13 -0500 [thread overview]
Message-ID: <200601070357.13954.len.brown@intel.com> (raw)
In-Reply-To: <200601070332.36654.len.brown@intel.com>
> git-update-index my-file
yes, that allowed the git commit to complete, thanks.
however, when i then merged that branch into another there seem to
be some phantom conflicts on the very same files.
Do I understand all this output to mean that git attempted two
different merges, and discarded the 1st attempt in favor of the second?
thanks,
-Len
$ /lab/bin/git.merge acpica test
Merging test with ed03f430cdc8c802652467e9097606fedc2c7abc
Merging:
e3627f3165301a7d946c2dc40be93f744f441c30 Auto-update from upstream
ed03f430cdc8c802652467e9097606fedc2c7abc Pull pnpacpi into acpica branch
found 2 common ancestor(s):
0aec63e67c69545ca757a73a66f5dcf05fa484bf [PATCH] Fix posix-cpu-timers sched_time accumulation
ed349a8a0a780ed27e2a765f16cee54d9b63bfee [ACPI] fix pnpacpi regression resulting from ACPICA 20051117
Merging:
0aec63e67c69545ca757a73a66f5dcf05fa484bf [PATCH] Fix posix-cpu-timers sched_time accumulation
ed349a8a0a780ed27e2a765f16cee54d9b63bfee [ACPI] fix pnpacpi regression resulting from ACPICA 20051117
found 1 common ancestor(s):
927fe18397b3b1194a5b26b1d388d97e391e5fd2 Pull 5165 into release branch
Auto-merging arch/i386/kernel/mpparse.c
Auto-merging include/asm-x86_64/mpspec.h
Auto-merging arch/ia64/pci/pci.c
Auto-merging drivers/acpi/utilities/utmisc.c
CONFLICT (content): Merge conflict in drivers/acpi/utilities/utmisc.c
Auto-merging include/acpi/acglobal.h
CONFLICT (content): Merge conflict in include/acpi/acglobal.h
Auto-merging drivers/acpi/scan.c
Auto-merging drivers/acpi/pci_link.c
Merge bfaa3a0777f0fc3b82831cb1daf286f8ac3b4c8d, made by recursive.
drivers/pnp/pnpacpi/rsparser.c | 48 +++++++++++++++++++++++++++++++++++++---
1 files changed, 44 insertions(+), 4 deletions(-)
$
next prev parent reply other threads:[~2006-01-07 8:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-07 8:32 needs merge Len Brown
2006-01-07 8:41 ` Junio C Hamano
2006-01-07 8:57 ` Len Brown [this message]
2006-01-07 10:28 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2006-01-07 10:33 Brown, Len
2006-01-07 21:06 ` Junio C Hamano
2006-01-10 5:21 ` Daniel Barkalow
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=200601070357.13954.len.brown@intel.com \
--to=len.brown@intel.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 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).