From: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
To: roberto.foglietta@linuxteam.org
Cc: isar-users@googlegroups.com
Subject: Re: [PATCH v6] suggested changes for reproducibility patchset v6
Date: Sun, 15 Jan 2023 23:01:16 +0100 [thread overview]
Message-ID: <CAJGKYO4MZLi7mToxZTuLKcmSJtXRcgP1vsP94wB7h+E1RHjw0g@mail.gmail.com> (raw)
In-Reply-To: <20230115215310.732295-1-roberto.foglietta@linuxteam.org>
On Sun, 15 Jan 2023 at 22:53, <roberto.foglietta@linuxteam.org> wrote:
>
> v.6: the 1st part of the warning shows up each time the epoch is used
> while the 2nd line appears only when some files has been touched
> This allows the user to know the current situation aboat epoch.
>
Please ignore this one, I missed one commit, sorry.
next prev parent reply other threads:[~2023-01-15 22:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-15 21:53 roberto.foglietta
2023-01-15 22:01 ` Roberto A. Foglietta [this message]
2023-01-15 22:31 ` Florian Bezdeka
2023-01-15 22:46 ` Roberto A. Foglietta
2023-01-17 11:53 ` Florian Bezdeka
2023-01-17 13:10 ` Roberto A. Foglietta
2023-01-25 16:38 ` Roberto A. Foglietta
2023-01-16 2:55 ` Moessbauer, Felix
2023-01-16 9:36 ` Roberto A. Foglietta
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=CAJGKYO4MZLi7mToxZTuLKcmSJtXRcgP1vsP94wB7h+E1RHjw0g@mail.gmail.com \
--to=roberto.foglietta@gmail.com \
--cc=isar-users@googlegroups.com \
--cc=roberto.foglietta@linuxteam.org \
/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