On Fri, 18 Jun 2021 at 12:05, Tobias Burnus wrote: > But with -p added, it becomes rather nice. For instance: > > git diff |./contrib/mklog.py -b foo/12394 -b 100123 -p > > nows prints: > > PR c++/12394 - internal compiler error: in write_type, at cp/mangle.c:1517 > PR fortran/100123 - -ftree-fre gives incorrect result in subroutine with > array declared as length 1 > > PR c++/12394 > PR fortran/100123
Now that we put these PR cmpt/nnnn lines before the xxx/ChangeLog entries, is there any reason to indent them with a TAB? If we didn't require the TAB before them, then the lines added by -p would serve the same purpose, and we wouldn't need to repeat them So instead of requiring "^\tPR .*/\d+$" for the PR entry, require "^\t?PR ([^/]+)/\d+" That would allow the existing convention, but also allow these to be used in their place: PR c++/12394 - internal compiler error: in write_type, at cp/mangle.c:1517 PR fortran/100123 - -ftree-fre gives incorrect result in subroutine with array declared as length 1
