News for hackers. Stuff that matters.
Re:Using Git commit message templates to write better commit... by ransom1538 on Thursday January 13, 2022 @12:26AM (#29917186)
I use this one from "How To Write Unmaintainable Code".

/*

/* Procedure Name:

/*

/* Original procedure name:

/*

/* Author:

/*

/* Date of creation:

/*

/* Dates of modification:

/*

/* Modification authors:

/*

/* Original file name:

/*

/* Purpose:

/*

/* Intent:

/*

/* Designation:

/*

/* Classes used:

/*

/* Constants:

/*

/* Local variables:

/*

/* Parameters:

/*

/* Date of creation:

/*

/* Purpose:

* /

Re:Using Git commit message templates to write better commit... by mns on Thursday January 13, 2022 @09:51AM (#29921324)
I'm reading the comments here and thinking I'm some outdated greybeard. Do people actually spend more time now trying to write commit messages than doing actual work? I would never put any of my teams to do something like this, do actual developers LIKE spending more time to actually write these messages? Is code today so hard to understand and read (what about comments) that you need these things for reviews?
Re:Using Git commit message templates to write better commit... by marginalia_nu on Thursday January 13, 2022 @04:59AM (#29918909)
You should just fill out a TPS report instead.