On Fri, Jan 5, 2018 at 6:55 PM, Michał Górny wrote:
> W dniu pią, 05.01.2018 o godzinie 23∶09 +0100, użytkownik Kristian
> Fiskerstrand napisał:
> > On 01/05/2018 10:28 PM, Aaron W. Swenson wrote:
> > > On 2018-01-05 15:16, William Hubbs wrote:
> > > > If we have a default
W dniu pią, 05.01.2018 o godzinie 23∶09 +0100, użytkownik Kristian
Fiskerstrand napisał:
> On 01/05/2018 10:28 PM, Aaron W. Swenson wrote:
> > On 2018-01-05 15:16, William Hubbs wrote:
> > > If we have a default expiration, it should be one year after the date
> > > posted to go along with our
On 01/05/2018 11:47 PM, Kristian Fiskerstrand wrote:
> On 01/05/2018 11:40 PM, Alec Warner wrote:
>>> I might sound like a broken CD here, but why define the expiration as
>>> part of the news format instead of specifying it in the package manager
>>> as a user defined variable? Various use cases
On 01/05/2018 11:40 PM, Alec Warner wrote:
>> I might sound like a broken CD here, but why define the expiration as
>> part of the news format instead of specifying it in the package manager
>> as a user defined variable? Various use cases requires different
>> treatment, so leaving it up to user
On Fri, Jan 5, 2018 at 5:09 PM, Kristian Fiskerstrand
wrote:
> On 01/05/2018 10:28 PM, Aaron W. Swenson wrote:
> > On 2018-01-05 15:16, William Hubbs wrote:
> >> If we have a default expiration, it should be one year after the date
> >> posted to go along with our current policy
On 01/05/2018 10:28 PM, Aaron W. Swenson wrote:
> On 2018-01-05 15:16, William Hubbs wrote:
>> If we have a default expiration, it should be one year after the date
>> posted to go along with our current policy of not supporting things that
>> are older than a year.
>>
>> William
>
> I thought it
On 2018-01-05 15:16, William Hubbs wrote:
> If we have a default expiration, it should be one year after the date
> posted to go along with our current policy of not supporting things that
> are older than a year.
>
> William
I thought it was three years.
At any rate, I think a year is too
On Fri, Jan 05, 2018 at 09:01:26AM -0500, Alec Warner wrote:
> On Fri, Jan 5, 2018 at 5:08 AM, Ulrich Mueller wrote:
> > > +In news item format ``>2.0``, this field is mandatory.
> >
> > I think it should not be mandatory, for the purpose of the tools
> > dealing with news
> On Fri, 5 Jan 2018, Alec Warner wrote:
> Latest version.
> I still want to discuss whether Expires is Mandatory or Optional and how that
> actually ends up being used.
If it is going to be mandatory, then we need to allow a special value
like "never" which would indicate that an item will
On Fri, Jan 5, 2018 at 4:00 AM, Michał Górny wrote:
> W dniu czw, 04.01.2018 o godzinie 20∶20 -0500, użytkownik Alec Warner
> napisał:
> > The attached patch proposes a new news item format (2.1).
> >
> > In format 2.1, the Expires: header is mandatory.
> >
> > PMs can detect
Latest version.
I still want to discuss whether Expires is Mandatory or Optional and how
that actually ends up being used.
-A
On Fri, Jan 5, 2018 at 9:01 AM, Alec Warner wrote:
>
>
> On Fri, Jan 5, 2018 at 5:15 AM, wrote:
>
>> January 5, 2018 3:58 AM,
On Fri, Jan 5, 2018 at 5:15 AM, wrote:
> January 5, 2018 3:58 AM, "Alec Warner" wrote:
> > ... snip ...
> > + compatability with GLEP 45 [#glep-45]_. Translations should use the
> date of
> > + the original news item. An item is expired if the current
On Fri, Jan 5, 2018 at 5:08 AM, Ulrich Mueller wrote:
> > On Thu, 4 Jan 2018, Alec Warner wrote:
>
> > Brief amendment. In the case where the PM cannot parse the expires
> header; it
> > should assume the item is not expired and display it (e.g. it should fail
> > open.)
>
>
January 5, 2018 3:58 AM, "Alec Warner" wrote:
> ... snip ...
> + compatability with GLEP 45 [#glep-45]_. Translations should use the date of
> + the original news item. An item is expired if the current date in UTC is
> + greater than the expiration date of the item. Package
> On Thu, 4 Jan 2018, Alec Warner wrote:
> Brief amendment. In the case where the PM cannot parse the expires header; it
> should assume the item is not expired and display it (e.g. it should fail
> open.)
> Updated patch attached.
> + ``Expires:``
> +Date of expiration, in
W dniu czw, 04.01.2018 o godzinie 20∶20 -0500, użytkownik Alec Warner
napisał:
> The attached patch proposes a new news item format (2.1).
>
> In format 2.1, the Expires: header is mandatory.
>
> PMs can detect whether a given news item is "expired" by comparing the
> current date in UTC to the
On Thu, Jan 4, 2018 at 8:20 PM, Alec Warner wrote:
> The attached patch proposes a new news item format (2.1).
>
> In format 2.1, the Expires: header is mandatory.
>
> PMs can detect whether a given news item is "expired" by comparing the
> current date in UTC to the expired
The attached patch proposes a new news item format (2.1).
In format 2.1, the Expires: header is mandatory.
PMs can detect whether a given news item is "expired" by comparing the
current date in UTC to the expired date.
Expired news items should not be shown to users.
Once this is accepted and
On Wed, Jan 3, 2018 at 6:07 AM, Ulrich Mueller wrote:
> > On Tue, 2 Jan 2018, Alec Warner wrote:
>
> > Problem:
> > New stages have numerous news items listed that are likely not
> > relevant, but are shown due to limitations in the filtering in NEWS
> > items. E.g. on a
On 01/03/2018 03:13 PM, Kristian Fiskerstrand wrote:
> On 01/03/2018 02:45 PM, Ciaran McCreesh wrote:
>> On Wed, 3 Jan 2018 12:23:33 +0100
>> Kristian Fiskerstrand wrote:
>>> Do we necessarily need to do even that? A package manager could have a
>>> feature to mask based on other
On 01/03/2018 02:45 PM, Ciaran McCreesh wrote:
> On Wed, 3 Jan 2018 12:23:33 +0100
> Kristian Fiskerstrand wrote:
>> Do we necessarily need to do even that? A package manager could have a
>> feature to mask based on other heuristics without changing the format,
>> e.g all
On Wed, 3 Jan 2018 12:23:33 +0100
Kristian Fiskerstrand wrote:
> Do we necessarily need to do even that? A package manager could have a
> feature to mask based on other heuristics without changing the format,
> e.g all messages from before X, presumably with a switch to show
On 01/03/2018 12:07 PM, Ulrich Mueller wrote:
>> On Tue, 2 Jan 2018, Alec Warner wrote:
>
>> Problem:
>> New stages have numerous news items listed that are likely not
>> relevant, but are shown due to limitations in the filtering in NEWS
>> items. E.g. on a recent stage3:
>
>> [...]
>
> We
On 01/03/2018 06:07 AM, Ulrich Mueller wrote:
>> On Tue, 2 Jan 2018, Alec Warner wrote:
>> Problem:
>> New stages have numerous news items listed that are likely not
>> relevant, but are shown due to limitations in the filtering in NEWS
>> items. E.g. on a recent stage3:
>> [...]
> We could
> On Tue, 2 Jan 2018, Alec Warner wrote:
> Problem:
> New stages have numerous news items listed that are likely not
> relevant, but are shown due to limitations in the filtering in NEWS
> items. E.g. on a recent stage3:
> [...]
We could add an "Expires:" header to the news item format, and
On 01/03/2018 05:53 AM, Michał Górny wrote:
> W dniu wto, 02.01.2018 o godzinie 19∶13 -0500, użytkownik Alec Warner
> napisał:
>> Problem:
>>
>> New stages have numerous news items listed that are likely not relevant,
>> but are shown due to limitations in the filtering in NEWS items. E.g. on a
>>
W dniu wto, 02.01.2018 o godzinie 19∶13 -0500, użytkownik Alec Warner
napisał:
> Problem:
>
> New stages have numerous news items listed that are likely not relevant,
> but are shown due to limitations in the filtering in NEWS items. E.g. on a
> recent stage3:
>
> nspawntest / # eselect news
+1
signature.asc
Description: Digital signature
+1
There is also https://www.gentoo.org/support/news-items/ if needed
signature.asc
Description: Digital signature
29 matches
Mail list logo