From: akuster808 <akuster808@gmail.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [dizzy][PATCH 0/2] Backport fixes for git-perltools split
Date: Tue, 30 Dec 2014 19:35:57 -0800 [thread overview]
Message-ID: <54A36F1D.7090901@gmail.com> (raw)
In-Reply-To: <1895049.K8DhQhocfW@peggleto-mobl5.ger.corp.intel.com>
Hello Paul,
On 12/30/2014 12:39 PM, Paul Eggleton wrote:
> Hi Armin,
>
> On Tuesday 30 December 2014 10:17:05 akuster wrote:
>> On 12/30/2014 09:02 AM, Paul Eggleton wrote:
>>> The following changes since commit
> 1cf1edcd28a002291622d04dd2d0ee2c67e329e4:
>>> buildtools-tarball: package all of Python (2014-12-11 16:34:01 +0000)
>>>
>>> are available in the git repository at:
>>> git://git.openembedded.org/openembedded-core-contrib
>>> paule/dizzy-git-tools
>>> http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=
>>> paule/dizzy-git-tools>
>>> Jackie Huang (1):
>>> packagegroup-self-hosted: add git-perltools
>>
>> This change is in that gray area "does this really need to be back
>> ported decision make processed", so I did not include it.
>
> I would argue this is of a similar order as the other fix. The tools that the
> git-perltools package contains were in the build appliance already until git-
> perltools was split out, so it's fixing a regression (though I think that
> regression happened in the 1.6 timeframe rather than 1.7 FWIW).
Thanks for the clarification.
This should be included then.
Regards,
- -armin
>
> Cheers,
> Paul
>
next prev parent reply other threads:[~2014-12-31 3:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-30 17:02 [dizzy][PATCH 0/2] Backport fixes for git-perltools split Paul Eggleton
2014-12-30 17:02 ` [dizzy][PATCH 1/2] packagegroup-self-hosted: add git-perltools Paul Eggleton
2014-12-30 17:02 ` [dizzy][PATCH 2/2] buildtools-tarball: restore missing git tools Paul Eggleton
2014-12-30 18:17 ` [dizzy][PATCH 0/2] Backport fixes for git-perltools split akuster
2014-12-30 20:39 ` Paul Eggleton
2014-12-31 3:35 ` akuster808 [this message]
2015-01-05 20:50 ` akuster808
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=54A36F1D.7090901@gmail.com \
--to=akuster808@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.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