On 7/16/20 2:37 PM, Ben Cotton wrote:
On Thu, Jul 16, 2020 at 4:20 PM Jonathan Wakely
wrote:
FCP33 seems a bit cryptic. F33 CHANGE is self-explanatory.
Agreed. No need to invent initialisms unnecessarily.
I could go with something like:
F$version Change proposal: $title - $type
For
On Thu, Jul 16, 2020 at 4:20 PM Jonathan Wakely
wrote:
>
> FCP33 seems a bit cryptic. F33 CHANGE is self-explanatory.
>
Agreed. No need to invent initialisms unnecessarily.
I could go with something like:
> F$version Change proposal: $title - $type
For example:
> F33 Change proposal: Replace
On 7/16/20 1:19 PM, Jonathan Wakely wrote:
On 16/07/20 08:39 +, Zbigniew Jędrzejewski-Szmek wrote:
On Wed, Jul 15, 2020 at 11:49:13AM -0700, Samuel Sieb wrote:
On 7/15/20 3:30 AM, Daniel P. Berrangé wrote:
>FCP33: Support PARSEC [Self-Contained]
>FCP33: PostgreSQL 31 [Self-Contained]
On 16/07/20 08:39 +, Zbigniew Jędrzejewski-Szmek wrote:
On Wed, Jul 15, 2020 at 11:49:13AM -0700, Samuel Sieb wrote:
On 7/15/20 3:30 AM, Daniel P. Berrangé wrote:
>FCP33: Support PARSEC [Self-Contained]
>FCP33: PostgreSQL 31 [Self-Contained]
>FCP33: Policy for Modules in Fedora and Fedora
On Wed, Jul 15, 2020 at 11:49:13AM -0700, Samuel Sieb wrote:
> On 7/15/20 3:30 AM, Daniel P. Berrangé wrote:
> >FCP33: Support PARSEC [Self-Contained]
> >FCP33: PostgreSQL 31 [Self-Contained]
> >FCP33: Policy for Modules in Fedora and Fedora ELN [Self-Contained]
> >FCP33: Golang 1.15 [Late,
On 7/15/20 3:30 AM, Daniel P. Berrangé wrote:
FCP33: Support PARSEC [Self-Contained]
FCP33: PostgreSQL 31 [Self-Contained]
FCP33: Policy for Modules in Fedora and Fedora ELN [Self-Contained]
FCP33: Golang 1.15 [Late, System-Wide]
FCP33: X.org Utility Deaggregation [Self-Contained]
Yes!
On Wed, Jul 15, 2020 at 12:18:51PM +0200, Kevin Kofler wrote:
> Ben Cotton wrote:
> > As noted by Milan Crha, the existing format can result in threads that
> > are hard to distinguish when the subject is truncated by the width of
> > the mail client window. Screens are often pretty wide these
Ben Cotton wrote:
> As noted by Milan Crha, the existing format can result in threads that
> are hard to distinguish when the subject is truncated by the width of
> the mail client window. Screens are often pretty wide these days, but
> ~40 characters is still a lot to use.
On the other hand, the
On 29 June 2020 19:27:23 CEST, Samuel Sieb wrote:
>On 6/29/20 8:22 AM, Ben Cotton wrote:
>> I will replace
>> "Fedora Change proposal: "
>>
>> with
>> " - Fedora Change proposal"
>>
>> As noted by Milan Crha, the existing format can result in threads that
>> are hard to distinguish when
On 6/29/20 8:22 AM, Ben Cotton wrote:
I will replace
"Fedora Change proposal: "
with
" - Fedora Change proposal"
As noted by Milan Crha, the existing format can result in threads that
are hard to distinguish when the subject is truncated by the width of
the mail client window. Screens are
Just in case anyone is parsing the subject line of change proposal
announcements (I really hope not, but if you are, please let me know
off-list what your use case is. I'm curious), I'm going to make a
change to how these are formatted.
I will replace
"Fedora Change proposal: "
with
" - Fedora
11 matches
Mail list logo
