What even

Posted Oct 21, 2024 19:00 UTC (Mon) by chexo4 (subscriber, #169500)
Parent article: A new kernel testing tree

The name is the only problem with this. Could they not have called it the “CI tree” or something

What even

Posted Oct 21, 2024 19:52 UTC (Mon) by sashal (✭ supporter ✭, #81842) [Link] (7 responses)

So many options, but naming is one thing I didn't want to bike-shed and 'linus-next' sounded great after a few beers in LPC so I just went with it :)

What even

Posted Oct 21, 2024 20:18 UTC (Mon) by Conan_Kudo (subscriber, #103240) [Link]

But, it's not even managed by Linus (or in his namespace), so it's kind of confusing to me.

What even

Posted Oct 22, 2024 5:08 UTC (Tue) by tlamp (subscriber, #108540) [Link] (1 responses)

On its own it might be fine, but as linux-next already exists and is often referenced, using linus-next has IMO a rather too strong and obvious confusion potential to go for that name.

And sure, naming is hard, but if there really were many options, ruling out those that clash with existing ones first seems like a good rule to narrow it a bit down.

Unsolicited proposals:
ci-next
for-mainline-ci

Or without the "CI" part, if that's just one thing the tree will be used for:
for-mainline
mainline-pending

But those may well be stupider than the other options you already have, I just did not want to write a critic on the chosen name without at least having something proposed, as just criticizing is easy.

Anyhow, thanks for your work!

LinuS-neSt

Posted Oct 22, 2024 7:45 UTC (Tue) by gmatht (guest, #58961) [Link]

For fans of the `g` flag of sed, may I propose an alternative that is slightly less likely to confuse than linus-next: linus-nest, a safe nest where Linus can keep fledgeling patches before they bash their way out of their shell and grow wings. :P

What even

Posted Oct 22, 2024 14:42 UTC (Tue) by dave_malcolm (subscriber, #15013) [Link]

This sounds horribly reminiscent of the use of the terms "gold owner" vs "goal donor" in Extreme Programming. The similarity may seem cute, but makes it impossible to discuss the topic over a noisy telephone line/conference call.

What even

Posted Oct 22, 2024 14:49 UTC (Tue) by marcH (subscriber, #57642) [Link] (1 responses)

> naming is one thing I didn't want to bike-shed

Obviously, no one is going to like a single character difference with something similar: success!

What even

Posted Oct 22, 2024 15:11 UTC (Tue) by geert (subscriber, #98403) [Link]

What about 28dfe2f9e617 and bf97a41e352a? ;-)

(hint: echo foo | sha1sum)

What even

Posted Oct 24, 2024 5:34 UTC (Thu) by unixbhaskar (guest, #44758) [Link]

:) He he he he he he he he he he he eh eh he... Naming is considered one of the hardest things in CS, and the convention continues.