From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH v4 - misc fixes 0/6] miscellaneous (minor) fixes
Date: Tue, 19 Nov 2019 17:56:35 +0100 [thread overview]
Message-ID: <20191119165635.h7kded3e75p6bk5j@yssyq.m.ilbers.de> (raw)
In-Reply-To: <8594de25-19a5-44a2-a4c0-cdf3a7b66f21@googlegroups.com>
On Fri, Nov 15, 2019 at 08:59:15AM -0800, chombourger@gmail.com wrote:
> Rebased locally (it did apply cleanly for me) - will anyway send v5
Yes, I've seen this behavior -- rebase is fine, git am fails. Usually that was
due the changes in the context lines (git am is possibly pickier than rebase
for whatever reason), but in this case I couldn't identify any changes in the
context lines, either.
> I can check what upstream does but to answer the other question, clean
> unfortunately leaves them behind
Isar -- yes, I had checked. The question was about the Yocto clean. Just in
case anyone has an answer.
> WICTMP is created with mktemp -d so I wonder if we would have to store it
> somewhere if we wanted to keep files in the buildchroot
> but delete them when we run do_clean
>
> should we introduce WIC_DEBUG?= "0" and keep them if it was set to "1"?
To make it clear, overall I'm willing to apply the series as is in v4. I'll
check v5 and let you know. I had thought about WIC_DEBUG, but I think it isn't
worth the effort. We don't modify the file, so having copies is useful only for
rare cases. OTOH, it eats space and the user might not be aware of that.
> that sounds like a good idea but do we want to expand the scope of this
> patch series?
No, I'd also like to avoid expanding the scope.
> As an aside, do we have a central TODO list where we can record things we
> really want to
> get done before we release something like 1.0? I recall seeing e-mails from
> different people
> with own lists. Should we have it in the repo so it's easy to find?
We used to have it. We've removed it after a discussion here and possibly
offline. Some issues have been moved to GitHub. Feel free to create new issues
there.
With kind regards,
Baurzhan.
next prev parent reply other threads:[~2019-11-19 16:56 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-21 9:34 [PATCH 0/4] " Cedric Hombourger
2019-10-21 9:34 ` [PATCH 1/4] wic-img: do not leave temporary files behind Cedric Hombourger
2019-10-21 9:34 ` [PATCH 2/4] isar-bootstrap: wipe out previously created rootfs with --one-file-system Cedric Hombourger
2019-10-21 9:34 ` [PATCH 3/4] base-apt-helper: fixed a few typos found in comments Cedric Hombourger
2019-10-21 9:34 ` [PATCH 4/4] patch: suffix patch files copied to .applied_patches with "~" Cedric Hombourger
2019-10-21 11:26 ` Henning Schild
2019-10-21 11:36 ` Cedric Hombourger
2019-10-21 12:43 ` Henning Schild
2019-10-21 12:53 ` Cedric Hombourger
2019-10-21 15:08 ` [PATCH v2 0/5] miscellaneous (minor) fixes Cedric Hombourger
2019-10-21 15:08 ` [PATCH v2 1/5] wic-img: do not leave temporary files behind Cedric Hombourger
2019-10-21 15:08 ` [PATCH v2 2/5] isar-bootstrap: wipe out previously created rootfs with --one-file-system Cedric Hombourger
2019-10-21 15:08 ` [PATCH v2 3/5] base-apt-helper: fixed a few typos found in comments Cedric Hombourger
2019-10-21 15:08 ` [PATCH v2 4/5] patch: suffix patch files copied to .applied_patches with "~" Cedric Hombourger
2019-10-21 15:10 ` [PATCH v2 5/5] hello: add a sample patch to exercise patch.bbclass against dpkg recipes Cedric Hombourger
2019-10-25 17:15 ` [PATCH 4/4] patch: suffix patch files copied to .applied_patches with "~" Jan Kiszka
2019-10-25 17:58 ` Cedric Hombourger
2019-11-05 12:52 ` [PATCH v3 0/6] miscellaneous (minor) fixes Cedric Hombourger
2019-11-05 12:53 ` [PATCH v3 1/6] wic-img: do not leave temporary files behind Cedric Hombourger
2019-11-05 12:53 ` [PATCH v3 2/6] isar-bootstrap: wipe out previously created rootfs with --one-file-system Cedric Hombourger
2019-11-05 12:53 ` [PATCH v3 3/6] base-apt-helper: fixed a few typos found in comments Cedric Hombourger
2019-11-05 12:53 ` [PATCH v3 4/6] ci_build.sh: delay "set -x" for a clean --help output Cedric Hombourger
2019-11-05 12:53 ` [PATCH v3 5/6] linux-custom: honor KERNEL_FILE setting Cedric Hombourger
2019-11-05 12:53 ` [PATCH v3 6/6] bitbake.conf: set name of the qemu-static binary to use for mipsel Cedric Hombourger
2019-11-08 9:23 ` [PATCH v4 - misc fixes 0/6] miscellaneous (minor) fixes Cedric Hombourger
2019-11-08 9:23 ` [PATCH v4 - misc fixes 1/6] wic-img: do not leave temporary files behind Cedric Hombourger
2019-11-15 13:38 ` Jan Kiszka
2019-11-15 13:42 ` Cedric Hombourger
2019-11-15 17:00 ` [PATCH v5 0/6] miscellaneous (minor) fixes Cedric Hombourger
2019-11-15 17:00 ` [PATCH v5 1/6] wic-img: do not leave temporary files behind Cedric Hombourger
2019-11-15 17:00 ` [PATCH v5 2/6] isar-bootstrap: wipe out previously created rootfs with --one-file-system Cedric Hombourger
2019-11-15 17:00 ` [PATCH v5 3/6] base-apt-helper: fixed a few typos found in comments Cedric Hombourger
2019-11-15 17:00 ` [PATCH v5 4/6] ci_build.sh: delay "set -x" for a clean --help output Cedric Hombourger
2019-11-15 17:00 ` [PATCH v5 5/6] linux-custom: honor KERNEL_FILE setting Cedric Hombourger
2019-11-15 17:00 ` [PATCH v5 6/6] bitbake.conf: set name of the qemu-static binary to use for mipsel Cedric Hombourger
2019-11-20 12:39 ` [PATCH v5 0/6] miscellaneous (minor) fixes Baurzhan Ismagulov
2019-11-08 9:23 ` [PATCH v4 - misc fixes 2/6] isar-bootstrap: wipe out previously created rootfs with --one-file-system Cedric Hombourger
2019-11-08 9:23 ` [PATCH v4 - misc fixes 3/6] base-apt-helper: fixed a few typos found in comments Cedric Hombourger
2019-11-08 9:23 ` [PATCH v4 - misc fixes 4/6] ci_build.sh: delay "set -x" for a clean --help output Cedric Hombourger
2019-11-08 9:24 ` [PATCH v4 - misc fixes 5/6] linux-custom: honor KERNEL_FILE setting Cedric Hombourger
2019-11-08 9:24 ` [PATCH v4 - misc fixes 6/6] bitbake.conf: set name of the qemu-static binary to use for mipsel Cedric Hombourger
2019-11-12 19:20 ` [PATCH v4 - misc fixes 0/6] miscellaneous (minor) fixes chombourger
2019-11-14 17:01 ` Baurzhan Ismagulov
2019-11-15 16:59 ` chombourger
2019-11-19 16:56 ` Baurzhan Ismagulov [this message]
2019-11-15 13:34 ` chombourger
2019-11-15 13:39 ` Baurzhan Ismagulov
2019-11-15 13:39 ` 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=20191119165635.h7kded3e75p6bk5j@yssyq.m.ilbers.de \
--to=ibr@radix50.net \
--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