From: "Klincov, Wadim" <wadim.klincov@siemens.com>
To: "amikan@ilbers.de" <amikan@ilbers.de>,
"Schild, Henning" <henning.schild@siemens.com>
Cc: "isar-users@googlegroups.com" <isar-users@googlegroups.com>,
"jan.kiszka@siemens.com" <jan.kiszka@siemens.com>,
"MOESSBAUER, FELIX JONATHAN" <felix.moessbauer@siemens.com>
Subject: Re: [PATCH] image: remove / entry from fstab template
Date: Fri, 14 Oct 2022 16:27:11 +0000 [thread overview]
Message-ID: <3f8b4770c18bac26dc84541416f363cb70535204.camel@siemens.com> (raw)
In-Reply-To: <0481351f-3113-0078-83a6-c5c78ddfe0de@ilbers.de>
On Fri, 2022-10-14 at 15:08 +0300, Anton Mikanovich wrote:
> 13.10.2022 18:00, Henning Schild wrote:
> > Am Tue, 11 Oct 2022 21:03:56 +0300
> > schrieb Anton Mikanovich <amikan@ilbers.de>:
> >
> > > Did anyone managed to test this on real projects?
> > Why do you ask, do you maybe see a risk? I tried it but that might
> > not
> > count since i proposed that patch.
> >
> > Henning
>
> I've asked it just in case any possible regressions.
> Hope there will be some replies if any, so lets merge the patch.
>
If it's still relevant: I've just tried it on a simple project on an HP
workstation with some custom options in `--fsoptions` and it works
well.
Wadim
next prev parent reply other threads:[~2022-10-14 16:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 11:46 Henning Schild
2022-10-04 11:53 ` Henning Schild
2022-10-04 11:54 ` Jan Kiszka
2022-10-04 12:21 ` Henning Schild
2022-10-11 18:03 ` Anton Mikanovich
2022-10-13 15:00 ` Henning Schild
2022-10-14 12:08 ` Anton Mikanovich
2022-10-14 16:27 ` Klincov, Wadim [this message]
2022-10-14 17:18 ` Anton Mikanovich
2022-10-14 12:10 ` Anton Mikanovich
2023-01-05 13:08 ` Florian Bezdeka
2023-01-06 4:58 ` Moessbauer, Felix
2023-01-06 8:54 ` Florian Bezdeka
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=3f8b4770c18bac26dc84541416f363cb70535204.camel@siemens.com \
--to=wadim.klincov@siemens.com \
--cc=amikan@ilbers.de \
--cc=felix.moessbauer@siemens.com \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.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