Stephen Leake wrote: > Ok, that is helpful. Perhaps that file should be mentioned in HACKING; > I would not think to look in Changelog for instructions on writing > commit messages :).
Sure, feel free to add something appropriate. ;) > But after you document the detailed changes to each file, you could step > back and write a summary of the change at the top of the message, > stating the overall purpose of the change. Yeah, it would certainly be nice to have an overview of the change before getting into the gory details. Cheers, Derek _______________________________________________ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
