On 19 September 2017 at 15:00, Mark Brown broonie@kernel.org wrote:
On Tue, Sep 19, 2017 at 02:38:25PM +0100, Milosz Wasilewski wrote:
On 13 September 2017 at 16:06, Mark Brown broonie@kernel.org wrote:
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?
I think the problem is that you are trying to use the internal name that bits of LKFT uses as a display name for end users and that's not going to end well - you probably need at least some blanks and some splitting things up.
I'm still waiting for a proposal what and how to change. As I wrote, I have no problem changing things.
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?
You're thinking about that the wrong way round - kernelci is displaying names from the tree it's working with, not making up new names for things which don't otherwise exist.
Right, so because you know that 'lsk' means everyone else know as well. The git repo is https://git.linaro.org/kernel/linux-linaro-stable.git. How does this map to 'lsk'? It's exactly the same story. 'lsk' is kernelci's internal project name and this somehow is OK while lkft's internal project names are not.
milosz
If you know what the LSK is and care about it then you know that's interesting, and the branch name there is exactly the branch name in the LSK tree so if you work with it you'll have seen that string. On my system I can do git operations on lsk/linux-linaro-lsk-v4.4-android since I named the remote for LSK. If someone is getting the LSK mails they'll probably have no problem.