From: Ingo Molnar <mingo@elte.hu>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: git-rerere observations and feature suggestions
Date: Wed, 18 Jun 2008 12:57:31 +0200 [thread overview]
Message-ID: <20080618105731.GA9242@elte.hu> (raw)
In-Reply-To: <20080616190911.GA7047@elte.hu>
* Ingo Molnar <mingo@elte.hu> wrote:
> And while asking for an arm i'd also like to ask for a leg, if i may:
> i'd love it if a "slightly conflicting" octopus merge of 85 topic
> trees would not result in one huge conflict commit that merges
> together 1000 commits into a single commit ;-)
>
> So right now in our -tip scripts work around this issue: we
> 'serialize' the topic merges despite having very nice opportunities
> for higher-order octopus merges. The integration would be a lot faster
> if we could use octopus merges and automated git-rerere. (Octopus
> merges would look much nicer as well in graphical representation as
> well, which counts too :-) )
just to demonstrate it, i tried today to do an octopus merge of 87 topic
branches:
git-merge build checkme core/checkme core/debugobjects core/futex-64bit
core/iter-div core/kill-the-BKL core/locking core/misc core/percpu
core/printk core/rcu core/rodata core/softirq core/softlockup
core/stacktrace core/topology core/urgent cpus4096 genirq kmemcheck
kmemcheck2 mm/xen out-of-tree pci-for-jesse safe-poison-pointers sched
sched-devel scratch stackprotector timers/clockevents timers/hpet
timers/hrtimers timers/nohz timers/posixtimers tip tracing/ftrace
tracing/ftrace-mergefixups tracing/immediates tracing/markers
tracing/mmiotrace tracing/mmiotrace-mergefixups tracing/nmisafe
tracing/sched_markers tracing/stopmachine-allcpus tracing/sysprof
tracing/textedit x86/apic x86/apm x86/bitops x86/build x86/checkme
x86/cleanups x86/cpa x86/cpu x86/defconfig x86/delay x86/gart x86/i8259
x86/idle x86/intel x86/irq x86/irqstats x86/kconfig x86/ldt x86/mce
x86/memtest x86/mmio x86/mpparse x86/nmi x86/numa x86/numa-fixes x86/pat
x86/pebs x86/ptemask x86/resumetrace x86/scratch x86/setup x86/smpboot
x86/threadinfo x86/timers x86/urgent x86/urgent-undo-ioapic x86/uv
x86/vdso x86/xen x86/xsave
it failed miserably:
warning: ignoring 066519068ad2fbe98c7f45552b1f592903a9c8c8; cannot
handle more than 25 refs
[...]
fatal: merge program failed
Automated merge did not work.
Should not be doing an Octopus.
Merge with strategy octopus failed.
this wasnt even for purposes of an integration run: all i wanted to do
was to pick up 2-3 new commits i have queued into 2-3 topic branches,
into the (throw-away) integration branch. All the other branches were
unmodified and already merged into the integration branch.
Hence i believe that the suggestions above by Git that i'm doing
something wrong are ... wrong :-)
My scripting around this would be a lot faster (less than 10 seconds
runtime versus a minute currently) and more robust if we could do such
higher-order octopus merges.
Ingo
next prev parent reply other threads:[~2008-06-18 10:59 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-16 11:01 git-rerere observations and feature suggestions Ingo Molnar
2008-06-16 11:09 ` Mike Hommey
2008-06-16 15:48 ` Pierre Habouzit
2008-06-16 15:57 ` Pierre Habouzit
2008-06-16 16:18 ` Sverre Rabbelier
2008-06-17 7:37 ` Karl Hasselström
2008-06-16 11:26 ` David Kastrup
2008-06-16 11:27 ` Theodore Tso
2008-06-16 12:38 ` David Kastrup
2008-06-16 19:52 ` Ingo Molnar
2008-06-16 20:25 ` Junio C Hamano
2008-06-16 20:46 ` Ingo Molnar
2008-06-16 21:37 ` Junio C Hamano
2008-06-16 18:46 ` Junio C Hamano
2008-06-16 19:09 ` Ingo Molnar
2008-06-16 20:50 ` Junio C Hamano
2008-06-22 9:47 ` [PATCH 1/5] rerere: rerere_created_at() and has_resolution() abstraction Junio C Hamano
2008-06-22 9:47 ` [PATCH 2/5] git-rerere: detect unparsable conflicts Junio C Hamano
2008-06-22 9:47 ` [PATCH 3/5] rerere: remove dubious "tail_optimization" Junio C Hamano
2008-06-22 9:48 ` [PATCH 4/5] t4200: fix rerere test Junio C Hamano
2008-06-22 9:48 ` [PATCH 5/5] rerere.autoupdate Junio C Hamano
2008-06-18 10:57 ` Ingo Molnar [this message]
2008-06-18 11:29 ` git-rerere observations and feature suggestions Miklos Vajna
2008-06-18 18:43 ` Ingo Molnar
2008-06-18 19:53 ` Miklos Vajna
2008-06-18 11:36 ` Ingo Molnar
2008-06-18 22:01 ` Jakub Narebski
2008-06-18 22:38 ` Miklos Vajna
2008-06-19 7:23 ` Karl Hasselström
2008-06-19 7:29 ` Miklos Vajna
2008-06-19 7:30 ` Junio C Hamano
2008-06-19 8:21 ` Karl Hasselström
2008-06-19 8:33 ` Miklos Vajna
2008-06-19 9:19 ` Karl Hasselström
2008-06-19 10:06 ` Miklos Vajna
2008-06-19 10:35 ` Karl Hasselström
2008-06-16 19:10 ` Junio C Hamano
2008-06-16 19:44 ` Ingo Molnar
2008-06-23 9:49 ` Ingo Molnar
2008-06-23 14:19 ` Peter Zijlstra
2008-06-23 14:26 ` Peter Zijlstra
2008-06-23 15:12 ` Jeff King
2008-06-23 15:22 ` Ingo Molnar
2008-06-16 20:11 ` Jakub Narebski
2008-06-17 10:24 ` Johannes Schindelin
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=20080618105731.GA9242@elte.hu \
--to=mingo@elte.hu \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).