[HeinzStuckeIt]

Funny how fast Git became entrenched as the way of doing things, though. Around 2010 I said in passing, in a forum discussion about how a FOSS project was getting along, “…you’d think someone could send in a patch…”, and I immediately got flamed by several people because no one used patches any more.

[Someone1234]

> Funny how fast Git became entrenched as the way of doing things, though.

It just really highlights how much better BitKeeper and then Git's design was compared to what came before. You then pile on being free/OSS, and being "proven" by an extremely large, well known, and successful project on top, and you have yourself explosive growth.

There are developers around these days who never had the displeasure of using the pre-Git source control offerings; it was rough.

[raverbashing]

Funnily enough the Linux Kernel still use patches (and of course Git has helpers to create and import patches)

[chris_wot]

Don’t they get emailed patch from git? Sorry if I’m super ignorant here, it’s interesting to me if they do!

[thaumasiotes]

> Funny how fast Git became entrenched as the way of doing things, though.

> ...and I immediately got flamed by several people because no one used patches any more.

How are these ideas connected? The intent of git is that you work with patches.

[HeinzStuckeIt]

For most people, git is that you work with pull requests, and already early on some bristled at the term “patches” which implied an obsolete way of working.