From: Jesse Barnes <jbarnes@virtuousgeek•org>
To: "Rafael J. Wysocki" <rjw@sisk•pl>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
Len Brown <lenb@kernel•org>,
linux-next@vger•kernel.org,
Linus Torvalds <torvalds@linux-foundation•org>
Subject: Re: linux-next: managing a web of git trees
Date: Fri, 13 Jun 2008 08:49:44 -0700 [thread overview]
Message-ID: <200806130849.45269.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <200806131045.45769.rjw@sisk.pl>
On Friday, June 13, 2008 1:45 am Rafael J. Wysocki wrote:
> > they are not the same commits:
> > "ACPI PM: acpi_pm_device_sleep_state() cleanup"
> > 06166780eb53685e72b589814d535d1f9948e761 in the pci tree
> > 0cc5ddb904162f611568d4db66ccd8af61dffc16 int the acpi tree
> > "ACPI PM: Remove obsolete Toshiba workaround"
> > 0e6859d49ff194e01afc229c996e3aefca1a0539 in the pci tree
> > f7259bd5d588d59816e1f4d5d4f3da9382916dac in the acpi tree
> >
> > In the acpi tree (I pull the test branch into linux-next) the former has
> > a different parent to the one on the pci tree since Jesse pulled your
> > "suspend" branch into his pci tree.
> >
> > So the git merge sees them as overlapping changes to the same file (as
> > well as the other commit above) and generates a conflict.
>
> Well, the commits will always be different, because they depend on the
> previous commits and those are different in both trees. The files they
> modify, however, should be exactly the same finally.
>
> I don't know how to handle that cleanly. :-(
Yuck, I thought they'd retain the same commit ids for some reason. OTOH if
the content is the same, resolving the conflicts should be trivial (git might
even do it automatically at merge time if it's identical?).
Linus, do you have any suggestions for this case? We've been trying to pull
different trees together to make merging & management easier, but it's not
working as smoothly as we'd like. My pull of Ingo's PCI changes worked
pretty well (after merging his branch all the identical commits ended up the
same), but my pull of Len's suspend branch didn't work that way...
Thanks,
Jesse
next prev parent reply other threads:[~2008-06-13 15:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-13 4:53 linux-next: manual merge of acpi tree Stephen Rothwell
2008-06-13 5:09 ` Len Brown
2008-06-13 6:02 ` Stephen Rothwell
2008-06-13 8:45 ` Rafael J. Wysocki
2008-06-13 15:49 ` Jesse Barnes [this message]
2008-06-13 16:01 ` linux-next: managing a web of git trees Linus Torvalds
2008-06-13 16:28 ` Jesse Barnes
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=200806130849.45269.jbarnes@virtuousgeek.org \
--to=jbarnes@virtuousgeek$(echo .)org \
--cc=lenb@kernel$(echo .)org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rjw@sisk$(echo .)pl \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=torvalds@linux-foundation$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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