Send plymouth mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.freedesktop.org/mailman/listinfo/plymouth
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of plymouth digest..."


Today's Topics:

   1. Re: olpc boot splash (Ray Strode)
   2. Re: olpc boot splash (Charlie Brej)
   3. [topic] in summary line (was Re: olpc boot splash) (Ray Strode)


----------------------------------------------------------------------

Message: 1
Date: Wed, 20 May 2009 17:34:34 -0400
From: Ray Strode <[email protected]>
Subject: Re: olpc boot splash
To: Peter Robinson <[email protected]>
Cc: [email protected]
Message-ID:
        <[email protected]>
Content-Type: text/plain; charset=UTF-8

Hi,

On Tue, May 5, 2009 at 2:40 PM, Ray Strode <[email protected]> wrote:
> The idea is, we can keep the C code upstream, along with good sample
> themes that use the C code. ?But keep the branding, trademarked
> images, etc, downstream.
>
> I'll probably be merging the branch to master soon unless you've got
> any concerns with it.
I've merged it to master now.

--Ray


------------------------------

Message: 2
Date: Wed, 20 May 2009 22:49:55 +0100
From: Charlie Brej <[email protected]>
Subject: Re: olpc boot splash
To: Ray Strode <[email protected]>
Cc: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=UTF-8; format=flowed

Ray Strode wrote:
> Hi,
> 
> On Tue, May 5, 2009 at 2:40 PM, Ray Strode <[email protected]> wrote:
>> The idea is, we can keep the C code upstream, along with good sample
>> themes that use the C code.  But keep the branding, trademarked
>> images, etc, downstream.
>>
>> I'll probably be merging the branch to master soon unless you've got
>> any concerns with it.
> I've merged it to master now.
> 
> --Ray

Do you want future commits to have the [something] tags on the first line?


------------------------------

Message: 3
Date: Thu, 21 May 2009 10:13:24 -0400
From: Ray Strode <[email protected]>
Subject: [topic] in summary line (was Re: olpc boot splash)
To: Charlie Brej <[email protected]>
Cc: [email protected]
Message-ID:
        <[email protected]>
Content-Type: text/plain; charset=UTF-8

Hi,

On Wed, May 20, 2009 at 5:49 PM, Charlie Brej <[email protected]> wrote:
> Ray Strode wrote:
>>> I'll probably be merging the branch to master soon unless you've got
>>> any concerns with it.
>>
>> I've merged it to master now.
> Do you want future commits to have the [something] tags on the first line?
It's an experiment I tried when I did the merge.  It's what the kernel
and a few other projects do.

The problem it solves is say, we're working on a splash plugin and in
the summary line we have:

Adjust time of progress animation

Which doesn't give any indication *which* splash plugin.  So we could
change it to

Adjust time of progress animation in the throbgress plugin

But then the summary line gets long and may get ellipsized before
saying which splash plugin.
I think the git maintainers recommend a summary line less than 50
characters to prevent it from getting ellipsized in some viewers.

If we do, instead

[throbgress] Adjust time of progress animation

then it's much more concise, although maybe a little noisier looking.

What do you think? I'm open to having them or not.

--Ray


------------------------------

_______________________________________________
plymouth mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/plymouth


End of plymouth Digest, Vol 8, Issue 12
***************************************

Reply via email to