The following patch series adds the ability to configure aliases for user-defined formats. The first two patches add infrastructure for the ease of adding additional formats, and infrastructure for defining format aliases, respectively. The final patch adds support for defining format aliases via a config option. This is the fourth version of the patch series. The most notable change from the last iteration is the removal of changes to other pretty-format options, such as the "conditional colors" patch and "%H/%h --abbrev" patches. I still think those were good patches, but the %H change in particular was controversial enough that it would have needlessly stood in the way of the rest of the series, and '%?C' looked out-of-place in this series without any other format changes. The removed patches will be worked on independently and will be submitted separately later. Jeff King noted an artifact of format.pretty.<name> left in the documentation, thanks. Junio asked for a better error message when looped-aliases were found, so that's been put in. The copyright notice for the added test has been changed to the standard boilerplate, because there's no reason to bring politics into a patch. Most other changes since the last iteration were simple style fixes, mostly a result of muscle memory from the coding conventions I use at work, though a couple of things (like not initializing static variables) were more towards the "you can do that? But my CS teacher in highschool told me not to!" end of the spectrum. Hopefully I've caught all the style problems this time. Will Palmer (3): pretty: make it easier to add new formats pretty: add infrastructure to allow format aliases pretty: add aliases for pretty formats Documentation/config.txt | 9 ++ Documentation/pretty-formats.txt | 7 ++- pretty.c | 154 ++++++++++++++++++++++++++++++++------ t/t4205-log-pretty-formats.sh | 66 ++++++++++++++++ 4 files changed, 212 insertions(+), 24 deletions(-) create mode 100755 t/t4205-log-pretty-formats.sh -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html