this post was submitted on 14 Jul 2025
389 points (95.8% liked)

linuxmemes

26317 readers
19 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
  • Don't get baited into back-and-forth insults. We are not animals.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn, no politics, no trolling or ragebaiting.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
  • 5. πŸ‡¬πŸ‡§ Language/язык/Sprache
  • This is primarily an English-speaking community. πŸ‡¬πŸ‡§πŸ‡¦πŸ‡ΊπŸ‡ΊπŸ‡Έ
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
  • 6. (NEW!) Regarding public figuresWe all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.
  • Keep discussions polite and free of disparagement.
  • We are never in possession of all of the facts. Defamatory comments will not be tolerated.
  • Discussions that get too heated will be locked and offending comments removed.
  • Β 

    Please report posts and comments that break these rules!


    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.

    founded 2 years ago
    MODERATORS
     
    top 50 comments
    sorted by: hot top controversial new old
    [–] rtxn@lemmy.world 16 points 1 week ago

    Locking comments. Had a good run, over half a day, but this was always headed for an emotional train wreck.

    [–] wesker 109 points 1 week ago

    main in the streets, master in the sheets

    [–] lilith267@lemmy.blahaj.zone 100 points 1 week ago (6 children)
    [–] rem26_art@fedia.io 43 points 1 week ago

    about to start using mommy for all my projects now

    [–] the_beber@feddit.org 22 points 1 week ago

    MOAB (mother of all branches)

    [–] alehc@slrpnk.net 20 points 1 week ago

    git checkout mommy

    [–] j4k3@lemmy.world 13 points 1 week ago
    load more comments (1 replies)
    [–] ozymandias117@lemmy.world 87 points 1 week ago (2 children)

    I get wanting to move away from "master," but why in the world didn't we use "trunk"

    It was already a standard name, and it fits "branches," etc.

    [–] dan@upvote.au 37 points 1 week ago* (last edited 1 week ago) (2 children)

    "trunk" is what it was called in SVN, too. Well, kind of. SVN didn't have a real concept of branching like Git does, but the main development would almost always happen in a root directory called "trunk".

    I'm not sure why Bitkeeper used "master", but that's why Git called it that (Git was originally built as a replacement for Bitkeeper).

    load more comments (2 replies)
    load more comments (1 replies)
    [–] rtxn@lemmy.world 83 points 1 week ago* (last edited 1 week ago) (4 children)

    It's a retroactive bastardization of the word based on one particular culture's one particular interpretation of it (master being, apparently, a slaveowner) that ignores both the much earlier meanings of master artisan or master craftsman (as opposed to journeyman and apprentice) and masterpiece (through which an artisan is recognised as a master), and the modern meaning of a master copy (like a master record in disc printing).

    This isn't like replacing the "master and slave" terminology with regard to connected devices. That one was warranted because it was often inaccurate and confusing. But forcing the adoption of main instead of master feels like someone got offended on someone else's behalf because a word looked superficially like that other bad word, and apparently we can't have an understanding that goes deeper than what letters it's made up of.

    Amerika ist wunderbar. This is an --initial-branch=master household.

    [–] PotatoesFall@discuss.tchncs.de 22 points 1 week ago (1 children)

    regardless of that, it's never inconvenienced me and it's still a net gain in readability, since main actually means what it means. have my shell scripts set up to use either one for any repo I'm in automatically.

    [–] rtxn@lemmy.world 17 points 1 week ago* (last edited 1 week ago) (2 children)

    Honestly it's not even about convenience. As far as breaking conventions go, this one has none-to-minimal impact -- existing master branches won't suddenly become invalid. But it's yet another instance of a subset of a subset of a subset of users getting to enforce their sensibilities for superficial reasons, and ultimately with zero effect regarding the cause they claim to represent; cultural and linguistic differences be damned.

    I'd love to be more specific, but I don't want the comments to turn into a warzone.

    And don't pretend like master doesn't mean what it means.

    [–] zeezee@slrpnk.net 16 points 1 week ago (1 children)

    And don't pretend like master doesn't mean what it means.

    Claiming that master on github stems from master recordings is not only disingenuous but also incorrect.

    As a FOSS alternative to BitKeeper, Git naturally reimplemented it's naming conventions as well - and because of the power of version control - we can actually check what the original meaning was derived from:

    We are then going to modify the file on both the master and slave repository and then merge the work.

    And yes I agree that GitHub just changing the name of the default branch while keeping their ICE contracts is performative as fuck - which imo means we should both boycott GitHub and use naming conventions that don't have a history related to one of the worst atrocities the global north has brought upon the world...

    load more comments (1 replies)
    load more comments (1 replies)
    load more comments (3 replies)
    [–] LovableSidekick@lemmy.world 83 points 1 week ago* (last edited 1 week ago) (4 children)

    I personally don't think the word "master" should be considered offensive - my wife has a master's degree in deaf education - but I've switched to "main" because that seems to be the convention now and it really doesn't have to be an issue.

    [–] i_am_not_a_robot@feddit.uk 33 points 1 week ago (2 children)

    There's no "slave" convention in git so I'm not sure how it can be considered an issue (I get that drives being master and slave is a bit icky). But then, what is it a master of?

    As others have said, "trunk" would have been a more sensible replacement.

    [–] rtxn@lemmy.world 29 points 1 week ago* (last edited 1 week ago) (2 children)

    It's a master the same way that an original recording (the final version before mass reproduction) is called a master; mixing and processing the raw media clips into such a recording is called mastering. It's a convention that has existed long before computers were a thing.

    load more comments (2 replies)
    load more comments (1 replies)
    load more comments (3 replies)
    [–] Lembot_0004@discuss.online 60 points 1 week ago (10 children)

    Master. I find this out of context fight against words pathetic.

    [–] CubitOom@infosec.pub 46 points 1 week ago* (last edited 1 week ago) (3 children)

    My scrum master said that we need new tickets to update the git branches and pipelines to use main instead of master since master was a bad word.

    I asked him what his job title was again and there was a pause.

    Then he said we can't say that we are going to groom the code base anymore.

    [–] childOfMagenta@jlai.lu 13 points 1 week ago

    Switch from your scrum main to your scrum alt.

    load more comments (2 replies)
    [–] corsicanguppy@lemmy.ca 11 points 1 week ago (4 children)

    I know someone with a master's degree from university.

    Well, he cut me a golden master copy of the track, anyway.

    load more comments (4 replies)
    load more comments (8 replies)
    [–] lemmyng@lemmy.ca 55 points 1 week ago (2 children)

    Just use main. I'm not bothered by either, but I'm not in the demographic that would be bothered by master, so I use main and STFU. It takes way less effort to switch to main (if you haven't already) than to come up with all this rhetoric about why master shouldn't trigger people.

    I would argue that it's best/easiest to leave existing projects on master, and just use main for new ones. Either way I agree, people arw reactionary af about this issue

    load more comments (1 replies)
    [–] finitebanjo@lemmy.world 51 points 1 week ago (3 children)

    I can work with either, but I cannot and will not forgive any deliberate changes from main to master.

    [–] NocturnalMorning@lemmy.world 39 points 1 week ago (1 children)

    If you have a main and a master branch in the same repo and you don't delete one at the very start of the project, God has abandoned the living bcz we're lost and he has forsaken all that is good in the world.

    [–] finitebanjo@lemmy.world 16 points 1 week ago (1 children)

    I didn't mean both simultaneously in the same project, lol.

    [–] zipsglacier@lemmy.world 42 points 1 week ago (3 children)

    Naming my branches like I name my word documents: master, main, main2, main2_FINAL, main_master, main_master_main, master_SUBMITTED, master_REVISED, master_REVISED_main_FINAL2,...

    load more comments (3 replies)
    load more comments (2 replies)
    [–] savvywolf@pawb.social 45 points 1 week ago (6 children)

    Main.

    Don't get me wrong, the whole debate is Microsoft just being performative (why not use your vast wealth to actually help people?). But honestly, putting the debate aside, "main" is just a clearer and more intuitive name.

    load more comments (6 replies)
    [–] BartyDeCanter 40 points 1 week ago (1 children)
    load more comments (1 replies)
    [–] codexarcanum@lemmy.dbzer0.com 38 points 1 week ago (2 children)

    No one commits to trunk anymore....

    [–] JigglySackles@lemmy.world 42 points 1 week ago* (last edited 1 week ago)
    load more comments (1 replies)
    [–] 0x01@lemmy.ml 34 points 1 week ago (4 children)

    The default branch for some projects is "production" since CD deploys on pushing to that branch

    For new projects, main. My thought is that even if master is not offensive, since the industry has generally made the change, the only reason to stick with master is stubbornness or hating political correctness, neither of which aligns with my self-view so I'll use main and move on.

    In general if people are genuinely hurt by the use of some words, I'm not sadistic so I'll avoid using them. From my perspective morality is the pursuit of the reduction of suffering, even if that suffering is internal.

    [–] natecox@programming.dev 19 points 1 week ago (3 children)

    It kills me that this take is so hard to find online.

    Did I think calling the main branch β€œmaster” was offensive before this controversy? No, I’d never even considered it.

    Does switching to calling it β€œmain” impact me, like… at all? Also no. It’s like the lowest effort change to make.

    If I can make my industry more welcoming to a more diverse group of people, that is a solid victory and way more important than the name of my primary git branch.

    load more comments (3 replies)
    load more comments (3 replies)
    [–] Pika@sh.itjust.works 32 points 1 week ago

    master

    I grew up with master, and main just feels weird.

    [–] avidamoeba@lemmy.ca 32 points 1 week ago

    Whatever the repo is setup with.

    [–] Integrate777@discuss.online 30 points 1 week ago

    I always rename my branch to main. Because it's shorter? That's the extent of my reasoning. Thanks for coming to my ted talk.

    [–] vivendi@programming.dev 27 points 1 week ago (14 children)

    Master. I find the whole "reasoning" behind the controversy absolute horseshit peddled by nontechnical people on the sidelines

    load more comments (14 replies)
    [–] infinitesunrise@slrpnk.net 25 points 1 week ago (1 children)

    No gods no master branches

    load more comments (1 replies)
    [–] killeronthecorner@lemmy.world 25 points 1 week ago (1 children)
    load more comments (1 replies)
    [–] RVGamer06@sh.itjust.works 21 points 1 week ago
    [–] lobut@lemmy.ca 20 points 1 week ago* (last edited 1 week ago) (3 children)

    If it uses master and it's too much trouble to get people to switch. It stays master until we can coordinate.

    If I'm starting a new project I use main.

    Why?

    It doesn't take much to do and it avoids any misunderstandings or arguments and we've got work to do. I don't particular care if you guys are "stuck" on master. If that's what it is and everyone wants to keep it that way, I don't have enough will to change it. If it's under my control, I will change it.

    load more comments (3 replies)
    [–] Brosplosion@lemmy.zip 19 points 1 week ago (2 children)

    I don't care which one you use, just don't change it once it's established. So many legacy Yocto projects got broken cause open source libraries changed their branch names.

    load more comments (2 replies)
    [–] ChuckTheMonkey@fedia.io 15 points 1 week ago (1 children)
    load more comments (1 replies)
    [–] pelya@lemmy.world 11 points 1 week ago

    I'm naming my production branch goshujin-sama

    load more comments
    view more: next β€Ί