From: "'Heinisch, Alexander' via isar-users" <isar-users@googlegroups.com>
To: "Kiszka, Jan" <jan.kiszka@siemens.com>,
"MOESSBAUER, Felix" <felix.moessbauer@siemens.com>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: RE: [PATCH] kas: Allow to define custom snapshot date
Date: Mon, 7 Oct 2024 10:57:49 +0000 [thread overview]
Message-ID: <AM7PR10MB3320D3516A49AC53B7A2DDEC867D2@AM7PR10MB3320.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <144150fd-3f1e-4182-bcf6-b3b55cea0f95@siemens.com>
> > The term "date" might be misleading here, as the value is a unix
> > timestamp. IIRC Alexander wanted to send a similar patch to specify
> > the apt snaptshot date in the upstream format (e.g. 20240702T082400Z),
> > making it easier to read.
> >
> > Either we rename that here to "Custom timestamp", or we wait for the
> > patch of Alexander and adapt accordingly.
Just posted: https://groups.google.com/g/isar-users/c/PzIksFyNDyc
BR Alexander
>
> This just exposes an existing isar variable. I can clarify the description of that string.
>
> I also tried some ad-hoc conversion, but the inline python support of bitbake is too limited for that (required "import datetime; ..."). We need some helper in the base class for that.
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/isar-users/AM7PR10MB3320D3516A49AC53B7A2DDEC867D2%40AM7PR10MB3320.EURPRD10.PROD.OUTLOOK.COM.
prev parent reply other threads:[~2024-10-07 10:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-04 10:20 'Jan Kiszka' via isar-users
2024-10-07 7:26 ` 'MOESSBAUER, Felix' via isar-users
2024-10-07 9:57 ` 'Jan Kiszka' via isar-users
2024-10-07 10:57 ` 'Heinisch, Alexander' via isar-users [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=AM7PR10MB3320D3516A49AC53B7A2DDEC867D2@AM7PR10MB3320.EURPRD10.PROD.OUTLOOK.COM \
--to=isar-users@googlegroups.com \
--cc=alexander.heinisch@siemens.com \
--cc=felix.moessbauer@siemens.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