On 13 September 2017 at 16:06, Mark Brown broonie@kernel.org wrote:
On Tue, Sep 12, 2017 at 09:28:51PM -0500, Tom Gall wrote:
On Tue, Sep 12, 2017 at 3:12 PM, Greg KH gregkh@google.com wrote:
WHat is "-rc-4.4-oe"? And why would I remember any of this?
first 2 bits are obvious, next is the user space being used. OE is Open Embedded as you might remember from past meetings.
I think Greg has a good point here, it's really not easy to see at a glance what the trees are.
People read things by pattern matching and the patterns that this is using are not like the patterns people normally use to describe kernels. At a glance the LKFT subjects look like they're for some derivative kernel, not the kernels they're actually for, since they just add elements separated by - too.
A couple of weeks ago we renamed the internal projects. I posted the proposal of naming scheme and there were no comments. I'm perfectly OK to change the names we're using, but what should we change them to? Is there any better naming convention to use?
Kernel maintainers get a lot of e-mail, often poorly directed. Being able to quickly figure out what to pay attention to is key, and for a lot of us we're doing that based on the subject lines of messages. As ever look at what the other bots are doing, what you're sending now are internal names for jobs that the infrastructure uses not display names for end users.
from kernelci: lsk/linux-linaro-lsk-v4.4-android How is that different to what lkft sends? How am I supposed to know what 'lsk' means without opening the email?
milosz
You snipped the link that describes the report, terms contained within etc.
Honestly if we're expecting someone to open the e-mail and then follow a link to figure out if this is something interesting to them then that's not success.
Lts-dev mailing list Lts-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lts-dev