I'm writing to propose the creation of a universal remote-ID file within
the api.git or gentoo.git in the metadata/ directory. Currently, we have
eight different locations that require manual updates for any future
changes, including my recent commit
On 22/09/2023 17.50, Alex Boag-Munroe wrote:
> On Fri, 22 Sept 2023 at 15:37, Sam James wrote:
>>
>>
>> Alex Boag-Munroe writes:
>>
>>> Any reason for the parseable parts to not be in an established human
>>> readable/editable format? e.g. the config ini style format, or TOML?
>>
>> The only
On Fri, 22 Sept 2023 at 15:37, Sam James wrote:
>
>
> Alex Boag-Munroe writes:
>
> > Any reason for the parseable parts to not be in an established human
> > readable/editable format? e.g. the config ini style format, or TOML?
>
> The only issue really is that depending on how it's done (do we
Alex Boag-Munroe writes:
> Any reason for the parseable parts to not be in an established human
> readable/editable format? e.g. the config ini style format, or TOML?
The only issue really is that depending on how it's done (do we do
it for the whole file, or just comments), it may need a new
Any reason for the parseable parts to not be in an established human
readable/editable format? e.g. the config ini style format, or TOML?
To crib from the OP example with something configparser understands:
[PREAMBLE]
Timestamp: 2023-09-21 15:07:42+00:00
Author: Arthur Zamarin
Justification:
Ulrich Mueller writes:
>> On Fri, 22 Sep 2023, Ulrich Mueller wrote:
>
>> On Fri, 22 Sep 2023, Florian Schmaus wrote:
>>> Some, including me, consider timestamps without timezone specifiers to
>>> be in local time (either of the consumer or producer of the
>>> timestamp). Hence, if you
On 22/09/2023 00.22, Ulrich Mueller wrote:
>> On Thu, 21 Sep 2023, Arthur Zamarin wrote:
>
>> = "Formal" format =
>
>> Each entry is composed of 2 parts: "#"-prefixed explanation block and
>> list of "${CATEGORY}/${PN}" packages. Entries are separated when a new
>> explanation block
> On Fri, 22 Sep 2023, Ulrich Mueller wrote:
> On Fri, 22 Sep 2023, Florian Schmaus wrote:
>> Some, including me, consider timestamps without timezone specifiers to
>> be in local time (either of the consumer or producer of the
>> timestamp). Hence, if you really must have UTC here, then
Hi,
On 2023/09/22 13:16, Florian Schmaus wrote:
On 21/09/2023 21.40, Arthur Zamarin wrote:
If this is a last-rite message, the last line must list the last-rite
last date (removal date) and the last-rite bug number. You can also list
FWIW, I would assume the last-rite date to be the date
On 21/09/2023 21.40, Arthur Zamarin wrote:
If this is a last-rite message, the last line must list the last-rite
last date (removal date) and the last-rite bug number. You can also list
FWIW, I would assume the last-rite date to be the date where the
package's last rites where initiated,
On 22/09/2023 12.21, Ulrich Mueller wrote:
>> On Fri, 22 Sep 2023, Oskari Pirhonen wrote:
>
>>> Each entry is composed of 2 parts: "#"-prefixed explanation block and
>>> list of "${CATEGORY}/${PN}" packages. Entries are separated when a new
>>> explanation block starts (meaning first
> On Fri, 22 Sep 2023, Florian Schmaus wrote:
> Some, including me, consider timestamps without timezone specifiers to
> be in local time (either of the consumer or producer of the
> timestamp). Hence, if you really must have UTC here, then at least
> consider making it explicit my requiring
> On Fri, 22 Sep 2023, Oskari Pirhonen wrote:
>> Each entry is composed of 2 parts: "#"-prefixed explanation block and
>> list of "${CATEGORY}/${PN}" packages. Entries are separated when a new
>> explanation block starts (meaning first "#"-prefixed line after packages
>> list). You may add
On 22/09/2023 08.39, Florian Schmaus wrote:
Some, including me, consider timestamps without timezone specifiers to
be in local time (either of the consumer or producer of the timestamp).
Hence, if you really must have UTC here, then at least consider making
it explicit my requiring the 'Z'
On 21/09/2023 23.48, Sam James wrote:
Ulrich Mueller writes:
On Thu, 21 Sep 2023, Florian Schmaus wrote:
The first line of the "#"-prefixed explanation block must be of the
format "${AUTHOR_NAME} <${EMAIL}> (${SINGLE_DATE})" when the date is of
format -MM-DD, in UTC timezone.
15 matches
Mail list logo
