From: Stephen Rothwell <sfr@canb.auug.org.au>
To: James Morris <jmorris@namei.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
git@vger.kernel.org, Linus <torvalds@linux-foundation.org>
Subject: linux-next: manual merge of the security-testing tree with the tree
Date: Thu, 30 Jun 2011 14:29:10 +1000 [thread overview]
Message-ID: <20110630142910.2fea4257.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 3680 bytes --]
Hi James,
Today's linux-next merge of the security-testing tree produced a large
number of conflicts in files not modified by the security-testing tree.
I assume that this is a bug in "git merge" but I cannot complete the
merge as such.
I have used the security-testing tree from next-20110628 for today.
More information for the git experts:
The security-testing tree is at
git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/security-testing-2.6.git
and I am trying to merge branch "next" into linux-next at commit
9fd8fab5e299a ("Merge remote-tracking branch 'voltage/for-next'").
I can merge commit 0e4ae0e0dec6 ("TOMOYO: Make several options
configurable") from the security testing tree without conflict and also
commit 25e75dff519b ("AppArmor: Fix masking of capabilities in complain
mode").
I cannot merge commit bcd05ca10420 ("Merge branch 'for-security' of
git://git.kernel.org/pub/scm/linux/kernel/git/jj/apparmor-dev into next")
which is the child of the above two commits.
The tree to commit 25e75dff519b only containes two simple commits
(modifying 2 files) and is based on v3.0-rc5. The tree to commit
bcd05ca10420 containes several commits and is based on commit
06e86849cf40 ("Merge branch 'pm-fixes' of
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/suspend-2.6") from
Linus' tree (between v3.0-rc2 and v3.0-rc2).
After attempting the merge I get this:
$ git status
# On branch master
# Changes to be committed:
#
# deleted: Documentation/ABI/testing/sysfs-class-backlight-driver-adp8870
# modified: Documentation/accounting/cgroupstats.txt
# modified: Documentation/cgroups/blkio-controller.txt
# modified: Documentation/cgroups/cgroups.txt
# modified: Documentation/cgroups/cpuacct.txt
# modified: Documentation/cgroups/cpusets.txt
.
. [lots elided]
.
# modified: tools/perf/util/PERF-VERSION-GEN
# modified: tools/perf/util/trace-event-parse.c
#
# Unmerged paths:
# (use "git add/rm <file>..." as appropriate to mark resolution)
#
# both modified: arch/arm/mach-shmobile/board-ag5evm.c
# both modified: arch/arm/mm/context.c
# both modified: arch/arm/mm/proc-v7.S
# both modified: arch/arm/plat-mxc/devices/platform-imx-dma.c
# both modified: arch/arm/plat-s5p/include/plat/map-s5p.h
# both modified: arch/m68k/Kconfig.nommu
# both modified: block/blk-throttle.c
# both modified: drivers/gpu/drm/nouveau/nouveau_fence.c
# deleted by them: drivers/net/usb/kalmia.c
# both modified: drivers/net/wireless/iwlegacy/iwl-dev.h
# both modified: drivers/net/wireless/iwlegacy/iwl4965-base.c
# both modified: drivers/net/wireless/iwlwifi/iwl-agn-rxon.c
# both modified: drivers/net/wireless/iwlwifi/iwl-agn.c
# both modified: drivers/net/wireless/rtlwifi/pci.c
# deleted by them: drivers/video/backlight/adp8870_bl.c
# both modified: fs/namei.c
# both modified: fs/nfs/nfs4proc.c
# both modified: fs/nfs/pnfs.c
# both modified: fs/proc/base.c
# both modified: net/bluetooth/rfcomm/sock.c
# both modified: net/ipv4/ip_output.c
# both modified: net/netfilter/ipvs/ip_vs_core.c
# both modified: sound/pci/hda/patch_via.c
# both modified: sound/soc/codecs/ad1836.h
# both modified: sound/soc/soc-cache.c
#
None of the "Unmerged paths" are modified in the tree I am merging in.
The linux-next tree will be published later today and James' tree is
available already (I can publis my copy of it if James modifies his).
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next reply other threads:[~2011-06-30 4:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-30 4:29 Stephen Rothwell [this message]
2011-06-30 4:33 ` linux-next: manual merge of the security-testing tree with the tree Stephen Rothwell
2011-06-30 4:39 ` Stephen Rothwell
2011-06-30 5:22 ` James Morris
2011-06-30 5:53 ` Stephen Rothwell
2011-06-30 7:25 ` Uwe Kleine-König
2011-06-30 9:30 ` Stephen Rothwell
2011-06-30 12:17 ` Uwe Kleine-König
2011-06-30 16:20 ` Linus Torvalds
2011-06-30 18:52 ` Junio C Hamano
2011-06-30 19:13 ` Jeff King
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=20110630142910.2fea4257.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=git@vger.kernel.org \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=torvalds@linux-foundation.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).