Ciro Santilli @cirosantilli 40

There are two ways to organize a project:

Some people like merges, but they are ugly and stupid. Rebase instead and keep linear history.

Linear history:

Branched history:

Here commits 6 and 7 are the so called "merge commits":

Which type of tree do you think will be easier to understand and maintain?

????

????????????

You may disconnect now if you still like branched history.

Just use limit instead, please. The French are particularly guilty of this.

Poor renaming choice.

Pseudo-fuck.

The key to solve conflicts is:

Or in other words, at every rebase conflict we have something like:Therefore there are 2 diffs that you have to understand and reconcile:

There are infinitely many primes with a neighbor not further apart than 70 million. This was the first such finite bound to be proven, and therefore a major breakthrough.

This implies that for at least one value (or more) below 70 million there are infinitely many repetitions, but we don't know which e.g. we could have infinitely many:or infinitely many:or infinitely many:or infinitely many:but we don't know which of those.

The Prime k-tuple conjecture conjectures that it is all of them.

Also, if 70 million could be reduced down to 2, we would have a proof of the Twin prime conjecture, but this method would only work for (k, k + 2).

A glitch is more precisely a software bug that is hard to reproduce. But it has also been used to mean a software bug that is not very serious.