Re: [PATCH v2 2/2] Increase minimum git commit ID abbreviation to 16 characters

2024-12-14 Thread Linus Torvalds
On Sat, 14 Dec 2024 at 08:03, Matthew Wilcox wrote: > > I have wondered about using a different encoding for the sha1. > Classic Ascii85 encoding is no good; it uses characters like '"\< > which interact poorly with every shell. RFC1924 is somewhat better, > but still uses characters that interac

Re: [PATCH v2 2/2] Increase minimum git commit ID abbreviation to 16 characters

2024-12-14 Thread Matthew Wilcox
On Thu, Dec 05, 2024 at 11:19:18AM -0800, Linus Torvalds wrote: > Why do I care? Because long git commit IDs are actually detrimental to > legibility. I try to make commit messages legible, and that very much > is the *point* of the short format. It's for people, not machinery. > > Yes, the basic

Re: [PATCH v2 2/2] Increase minimum git commit ID abbreviation to 16 characters

2024-12-13 Thread Geert Uytterhoeven
Hi Linus, On Thu, Dec 5, 2024 at 8:19 PM Linus Torvalds wrote: > On Thu, 5 Dec 2024 at 10:16, Geert Uytterhoeven > wrote: > > Hence according to the Birthday Paradox, collisions of 12-chararacter > > git commit IDs are imminent, or already happening. > > Note that ambiguous commit IDs are not e

Re: [PATCH v2 2/2] Increase minimum git commit ID abbreviation to 16 characters

2024-12-05 Thread Linus Torvalds
On Thu, 5 Dec 2024 at 10:16, Geert Uytterhoeven wrote: > > Hence according to the Birthday Paradox, collisions of 12-chararacter > git commit IDs are imminent, or already happening. Note that ambiguous commit IDs are not even remotely as scary as this implies. Yes, the current kernel tree has ov