From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/7] combo-layer enhancements
Date: Mon, 07 Nov 2011 12:16:29 +0000 [thread overview]
Message-ID: <9572836.16zuAUMiQO@helios> (raw)
In-Reply-To: <4F626E19-A84B-4FB7-B6E0-24EC9FC6691A@dominion.thruhere.net>
On Monday 07 November 2011 11:16:26 Koen Kooi wrote:
> With all the fixes in your branch does this allow creating a combo layer
> from scratch with all the history present?
If you expect that it will do that automatically with no conflict resolution
necessary, then the answer is no I'm afraid. My focus at least for one of
these patches was to get repo creation starting from the current revision
working with no hassle. Testing an import of the entire history just now
though did point out a trivial issue with empty commits which I have now fixed,
however, "git format-patch" (which is the basis for combo-layer) simply cannot
handle merges where a conflict was resolved, and AFAICT there is no way around
this. Typically we don't do merges in the OE-core or bitbake repositories so
this is not too serious an issue; however, there is at least one merge in the
OE-core history where there are changes that conflict (an example would be
76e51a83e1af6c95a8ba780d8d543ddda52e1597 and
3937aefbefda15a65436238a6c6f1485419c914b). When it gets to these you will have
to resolve the conflict by hand.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
prev parent reply other threads:[~2011-11-07 12:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-04 17:55 [PATCH 0/7] combo-layer enhancements Paul Eggleton
2011-11-04 17:55 ` [PATCH 1/7] scripts/combo-layer: handle merge commits Paul Eggleton
2011-11-04 17:55 ` [PATCH 2/7] scripts/combo-layer: make init set up initial component data Paul Eggleton
2011-11-04 17:55 ` [PATCH 3/7] scripts/combo-layer: tidy up config example Paul Eggleton
2011-11-04 17:55 ` [PATCH 4/7] scripts/combo-layer: make component repo branch configurable Paul Eggleton
2011-11-04 17:55 ` [PATCH 5/7] scripts/combo-layer: fix dirty repo check Paul Eggleton
2011-11-04 17:55 ` [PATCH 6/7] scripts/combo-layer: auto-commit updated config file Paul Eggleton
2011-11-04 17:55 ` [PATCH 7/7] scripts/combo-layer: improve some messages Paul Eggleton
2011-11-04 18:15 ` [PATCH 0/7] combo-layer enhancements Otavio Salvador
2011-11-07 10:14 ` Paul Eggleton
2011-11-07 10:16 ` Koen Kooi
2011-11-07 12:16 ` Paul Eggleton [this message]
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=9572836.16zuAUMiQO@helios \
--to=paul.eggleton@linux.intel.com \
--cc=koen@dominion.thruhere.net \
--cc=openembedded-core@lists.openembedded.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