From: chombourger@gmail.com
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH 1/1] bitbake: update to version 1.44.0
Date: Wed, 23 Oct 2019 23:58:06 -0700 (PDT) [thread overview]
Message-ID: <8ba37251-4ee6-40fb-b076-a6e75ab8e183@googlegroups.com> (raw)
In-Reply-To: <20191022155642.h7cofdpjco3rgqcl@yssyq.m.ilbers.de>
[-- Attachment #1.1: Type: text/plain, Size: 808 bytes --]
Thanks Baurzhan
Is this patch OK to merge then?
Cedric
On Tuesday, October 22, 2019 at 5:56:46 PM UTC+2, Baurzhan Ismagulov wrote:
>
> On Tue, Oct 22, 2019 at 09:41:59AM +0200, Cedric Hombourger wrote:
> > I have debated (with myself :)) and I agree that there are pros and cons
> > with each approach.
> > I ended up submitting a single commit at the end of the day to support
> > people needing to "git bisect".
> > I have otherwise no issues resubmitting the changes if we prefer to have
> the
> > bitbake upgrade clearly separated from the Isar changes (either way is
> fine
> > with me - @maintainers just let me know what your preference is!)
>
> Since the bitbake commit breaks stuff, I have to prefer :) a single
> commit. I
> agree it is ugly.
>
> With kind regards,
> Baurzhan.
>
[-- Attachment #1.2: Type: text/html, Size: 1047 bytes --]
next prev parent reply other threads:[~2019-10-24 6:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-21 14:19 [PATCH 0/1] update bitbake " Cedric Hombourger
2019-10-21 14:19 ` [PATCH 1/1] bitbake: update " Cedric Hombourger
2019-10-22 7:36 ` Henning Schild
2019-10-22 7:41 ` Cedric Hombourger
2019-10-22 15:56 ` Baurzhan Ismagulov
2019-10-24 6:58 ` chombourger [this message]
2019-10-24 19:44 ` Baurzhan Ismagulov
2019-11-05 12:36 ` chombourger
2019-11-06 6:01 ` Baurzhan Ismagulov
2019-11-06 6:02 ` Cedric Hombourger
2019-11-08 8:05 ` [PATCH 0/1] update bitbake " Jan Kiszka
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=8ba37251-4ee6-40fb-b076-a6e75ab8e183@googlegroups.com \
--to=chombourger@gmail.com \
--cc=isar-users@googlegroups.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