# # Bitkeeper,git (patch maintenance)
APLawrence.com -  Resources for Unix and Linux Systems, Bloggers and the self-employed

2005/05/02 Bitkeeper,git (patch maintenance)

I've removed advertising from most of this site and will eventually clean up the few pages where it remains.

While not terribly expensive to maintain, this does cost me something. If I don't get enough donations to cover that expense, I will be shutting the site down in early 2020.

If you found something useful today, please consider a small donation.



Some material is very old and may be incorrect today

© May 2005 Tony Lawrence

Kernel programmers need to keep track of patches. That's pretty obvious, but what isn't immediately obvious to those of us who aren't kernel developers is just how onerous that task is for Linux kernels. Enter Bitkeeper , a SCM (Source Code Management) tool that dulls the pain and attends to the nasty details, leaving the developer more time to focus on development.

But wait: Bitkeeper is a commercial product. Linux isn't about commercial products, right? Well no, but technically Bitkeeper isn't part of Linux; it's just something that developers could use to track their changes. And Bitkeeper itself quietly helped out by letting those developers use the tool for free. That was the status quo up till recently. There were people like Richard Stallman who warned that this was bad practice, but nobody pays attention to GNU/Richard.

But then Bitkeeper pulled the plug. No more freebies. Shoulda listened to Richard, I think. This was a choice of convenience over principle. It's not the only place Linux flunks the Purity test, but it was a big one.

So now kernel developers have to use something else. At the moment, that may be Linus Torvald's "git". And we leave the developers to work the details out for themselves.

There's another place where I think Linux packagers are making a big mistake, and that's Cups. Not that Cups isn't good, it is. But it's was also a commercial product and right now it is owned by Apple. I'm not saying that Apple is likely to cause problems (imagine if Microsoft bought it!), but the point is that they could. I'd just rather see unencumbered code.


If you found something useful today, please consider a small donation.



Got something to add? Send me email.





(OLDER)    <- More Stuff -> (NEWER)    (NEWEST)   

Printer Friendly Version

->
-> Bitkeeper,git (patch maintenance)


Inexpensive and informative Apple related e-books:

iOS 8: A Take Control Crash Course

Photos for Mac: A Take Control Crash Course

Take Control of the Mac Command Line with Terminal, Second Edition

Take Control of OS X Server

Photos: A Take Control Crash Course





More Articles by © Tony Lawrence



Related Articles




Printer Friendly Version


Related Articles

Have you tried Searching this site?

This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more.

Contact us


Printer Friendly Version





Solving today's problems with yesterday's technology,someday (Kevin Brooks Clark)




Linux posts

Troubleshooting posts


This post tagged:

Linux

Programming

Unix



Unix/Linux Consultants

Skills Tests

Unix/Linux Book Reviews

My Unix/Linux Troubleshooting Book

This site runs on Linode