Jonas Hahnfeld via Discussions on LilyPond development
writes:
> For SHA1, I'd recommend using more than 6 chars to avoid collisions.
> The Linux kernel encourages 12 characters [1], but I think we are good
> with less. $ git log --oneline currently shows 10 chars for the
> LilyPond repo, that sh
Am Freitag, den 07.02.2020, 12:37 -0500 schrieb Dan Eble:
> On Feb 7, 2020, at 10:39, Han-Wen Nienhuys <
> hanw...@gmail.com
> > wrote:
> > There are a couple of downsides to this format:
> > * The number takes up space in the
> >git log --format=short
>
> upside: the number appears in git log
+1 to all parts of the proposal from me.
pt., 7 lut 2020 o 16:39 Han-Wen Nienhuys napisał(a):
> Currently, on push most our commit messages look like:
>
> Issue XXX: Subject
>
> Body
> Body
>
>
> There are a couple of downsides to this format:
>
> * The number takes up space in the
>
On Feb 7, 2020, at 10:39, Han-Wen Nienhuys wrote:
>
> There are a couple of downsides to this format:
> * The number takes up space in the
>git log --format=short
upside: the number appears in git log —format=short
> * The number is meaningless without the site that hosts the tracker
exagg
Currently, on push most our commit messages look like:
Issue XXX: Subject
Body
Body
There are a couple of downsides to this format:
* The number takes up space in the
git log --format=short
output
* The number is meaningless without the site that hosts the tracker
Proposa
