[Slackbuilds-users] Commit messages by maintainers are truncated when committed.

Willy Sudiarto Raharjo willysr at slackbuilds.org
Fri Apr 6 18:46:10 UTC 2018

>> There is a limit of 68 characters on the commit messages.  Also, there
>> is not any automatic way of adding your extra text to the commit
>> messages, I have to do it manually, and if it's late at night and if
>> it's taken an hour to clean up a submission, sometimes I forget.
> To clarify... does that 68 characters include the category and program name?


> E.g. there's a build called "haskell/haskell-data-default-instances-containers"
> whose name is 49 characters long. The commit format also calls for a colon
> and a space after the name, so that'd be 51, leaving only 17 characters
> for the actual message... is this correct?


> Also... 68 is a very specific number. Curious to know where it comes from...

I don't have the exact answer for this one, but i'm guessing that it
would be for readability in the public update announcement as well as in
the git log.

"git log doesn’t do any special special wrapping of the commit messages.
With the default pager of less -S, this means your paragraphs flow far
off the edge of the screen, making them difficult to read. On an 80
column terminal, if we subtract 4 columns for the indent on the left and
4 more for symmetry on the right, we’re left with 72 columns."
for more info

Other projects (eg Linux kernel) also have their own numbers

Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180407/f79f755d/attachment.asc>

More information about the SlackBuilds-users mailing list