Extremely Linear Git History

#1

Post by zegl » Tue, Nov 22, 2022, 10:43 AM UTC

Extremely Linear Git History
westling.dev

Re: Extremely Linear Git History

#2

Post by enriquto » Tue, Nov 22, 2022, 11:13 AM UTC

I love linear git! Branches are very confusing for a nonempty set of people. For us, it is always clearer to work with explicit files in the main branch. You are implementing a new feature? Nice: just create a new file on the main branch and keep updating it until you add it to the tests, and later you call it from the main program. This system may break down on large teams, but when you are just a handful of grug-brained developers, it's perfectly appropriate.

Re: Extremely Linear Git History

#3

Post by davide_v » Tue, Nov 22, 2022, 11:16 AM UTC

I thought I was a very tidy person, then I saw this.

Re: Extremely Linear Git History

#4

Post by hoseja » Tue, Nov 22, 2022, 11:16 AM UTC

This is very silly.

Re: Extremely Linear Git History

#5

Post by zegl » Tue, Nov 22, 2022, 11:18 AM UTC

hoseja wrote: post #4

This is very silly.

Do not try this at home.

Re: Extremely Linear Git History

#6

Post by mjburgess » Tue, Nov 22, 2022, 11:18 AM UTC

enriquto wrote: post #2

I love linear git! Branches are very confusing for a nonempty set of people. For us, it is always clearer to work with explicit files in the main branch. You are implementing a new feature? Nice: just create a new file on the main branch and keep updating it until you add it to the tests, and later you call it from the main program. This system may break down on large teams, but when you are just a handful of grug-br…

That requires your programming language to identify files with modules, and with your system architecture to be extended by modules alone.

This is an ideal case, of course.

Re: Extremely Linear Git History

#7

Post by maxbond » Tue, Nov 22, 2022, 11:19 AM UTC

Has anyone tried using git alternatives like fossil in production? Did it work out? Did you build CI/CD around it?

Re: Extremely Linear Git History

#8

Post by Thev00d00 » Tue, Nov 22, 2022, 11:20 AM UTC

davide_v wrote: post #3

I thought I was a very tidy person, then I saw this.

Im not sure it is tidy to inject random junk into your commit message to get a hash prefix

Re: Extremely Linear Git History

#9

Post by unnouinceput » Tue, Nov 22, 2022, 11:23 AM UTC

Extremely Linear Git History...also known as SVN. Guess reinventing the wheel does get you to top HN.

Re: Extremely Linear Git History

#10

Post by enriquto » Tue, Nov 22, 2022, 11:24 AM UTC

mjburgess wrote: post #6

enriquto wrote: post #2

I love linear git! Branches are very confusing for a nonempty set of people. For us, it is always clearer to work with explicit files in the main branch. You are implementing a new feature? Nice: just create a new file on the main branch and keep updating it until you add it to the tests, and later you call it from the main program. This system may break down on large teams, but when you are just a handful of grug-br…

That requires your programming language to identify files with modules, and with your system architecture to be extended by modules alone. This is an ideal case, of course.

I don't understand your comment. The method that I describe only requires that the programming language ignores unused files. As far as I know, all modern programming languages have this feature.