Skip to main content
The -> then in last sentence. License -> signature in fourth paragraph.
Source Link

The --show-signature argument can be selected in the log popup but it is not actually passed to git log. Instead %G? is added to the value of the --format= argument.

That (%G?) causes some letter to be printed for each commit and the code that parses the log output detects that letter and uses it to determine what face should be used to display the commit message summary. The faces are named magit-signature-.... By default commits with "unproblematic" signatures are displayed the same way as regular text (i.e. like the default face), while other commits are displayed using some flashy color and therefore easily detected.

The reason the signatures are not shown in the log buffer is that Magit usually displays each commit on a single line. Displaying each commits signature on multiple lines would mess that up.


To actually find out what is wrong about the licensesignature you will have to visit the commit itself by pressing RET while point is on that commit in the log.

By default the revision buffer also does not show the signature. To show the signature you have to enable the --show-signature argument for the revision buffer also. To do so visit the revision buffer as usual. Then type D to change the diff arguments used in the current buffer. TheThen enable the respective argument using = g and finally save that as the default while also refreshing the current buffer using w.

The --show-signature argument can be selected in the log popup but it is not actually passed to git log. Instead %G? is added to the value of the --format= argument.

That (%G?) causes some letter to be printed for each commit and the code that parses the log output detects that letter and uses it to determine what face should be used to display the commit message summary. The faces are named magit-signature-.... By default commits with "unproblematic" signatures are displayed the same way as regular text (i.e. like the default face), while other commits are displayed using some flashy color and therefore easily detected.

The reason the signatures are not shown in the log buffer is that Magit usually displays each commit on a single line. Displaying each commits signature on multiple lines would mess that up.


To actually find out what is wrong about the license you will have to visit the commit itself by pressing RET while point is on that commit in the log.

By default the revision buffer also does not show the signature. To show the signature you have to enable the --show-signature argument for the revision buffer also. To do so visit the revision buffer as usual. Then type D to change the diff arguments used in the current buffer. The enable the respective argument using = g and finally save that as the default while also refreshing the current buffer using w.

The --show-signature argument can be selected in the log popup but it is not actually passed to git log. Instead %G? is added to the value of the --format= argument.

That (%G?) causes some letter to be printed for each commit and the code that parses the log output detects that letter and uses it to determine what face should be used to display the commit message summary. The faces are named magit-signature-.... By default commits with "unproblematic" signatures are displayed the same way as regular text (i.e. like the default face), while other commits are displayed using some flashy color and therefore easily detected.

The reason the signatures are not shown in the log buffer is that Magit usually displays each commit on a single line. Displaying each commits signature on multiple lines would mess that up.


To actually find out what is wrong about the signature you will have to visit the commit itself by pressing RET while point is on that commit in the log.

By default the revision buffer also does not show the signature. To show the signature you have to enable the --show-signature argument for the revision buffer also. To do so visit the revision buffer as usual. Then type D to change the diff arguments used in the current buffer. Then enable the respective argument using = g and finally save that as the default while also refreshing the current buffer using w.

added 460 characters in body
Source Link
tarsius
  • 26.3k
  • 4
  • 74
  • 111

The --show-signature argument can be selected in the log popup but it is not actually passed to git log. Instead %G? is added to the value of the --format= argument.

That (%G?) causes some letter to be printed for each commit and the code that parses the log output detects that letter and uses it to determine what face should be used to display the commit message summary. The faces are named magit-signature-.... By default commits with "unproblematic" signatures are displayed the same way as regular text (i.e. like the default face), while other commits are displayed using some flashy color and therefore easily detected.

The reason the signatures are not shown in the log buffer is that Magit usually displays each commit on a single line. Displaying each commits signature on multiple lines would mess that up.


To actually find out what is wrong about the license you will have to visit the commit itself by pressing RET while point is on that commit in the log.

The reasonBy default the signatures arerevision buffer also does not shownshow the signature. To show the signature you have to enable the --show-signature argument for the revision buffer also. To do so visit the revision buffer as usual. Then type D to change the diff arguments used in the logcurrent buffer is that Magit usually displays each commit on a single line. Displaying each commits signature on multiple lines would messThe enable the respective argument using = g and finally save that upas the default while also refreshing the current buffer using w.

The --show-signature argument can be selected in the log popup but it is not actually passed to git log. Instead %G? is added to the value of the --format= argument.

That (%G?) causes some letter to be printed for each commit and the code that parses the log output detects that letter and uses it to determine what face should be used to display the commit message summary. The faces are named magit-signature-.... By default commits with "unproblematic" signatures are displayed the same way as regular text (i.e. like the default face), while other commits are displayed using some flashy color and therefore easily detected.

To actually find out what is wrong about the license you will have to visit the commit itself by pressing RET while point is on that commit in the log.

The reason the signatures are not shown in the log buffer is that Magit usually displays each commit on a single line. Displaying each commits signature on multiple lines would mess that up.

The --show-signature argument can be selected in the log popup but it is not actually passed to git log. Instead %G? is added to the value of the --format= argument.

That (%G?) causes some letter to be printed for each commit and the code that parses the log output detects that letter and uses it to determine what face should be used to display the commit message summary. The faces are named magit-signature-.... By default commits with "unproblematic" signatures are displayed the same way as regular text (i.e. like the default face), while other commits are displayed using some flashy color and therefore easily detected.

The reason the signatures are not shown in the log buffer is that Magit usually displays each commit on a single line. Displaying each commits signature on multiple lines would mess that up.


To actually find out what is wrong about the license you will have to visit the commit itself by pressing RET while point is on that commit in the log.

By default the revision buffer also does not show the signature. To show the signature you have to enable the --show-signature argument for the revision buffer also. To do so visit the revision buffer as usual. Then type D to change the diff arguments used in the current buffer. The enable the respective argument using = g and finally save that as the default while also refreshing the current buffer using w.

edited body
Source Link
tarsius
  • 26.3k
  • 4
  • 74
  • 111

The --show-signature argument can be selected in the log popup but it is not actually passed to git log. Instead %G? is added to the value of the --format= argument.

That (%G?) causes some letter to be printed for each commit and the code that parses the log output detects that letter and uses it to determine what face should be used to display the commit message summary. The faces are named ~magit-signature-magit-signature-.... By default commits with "unproblematic" signatures are displayed the same way as regular text (i.e. like the . By default commits with "unproblematic" signatures are displayed the same way as regular text (i.e. like the default` face), while other commits are displayed using some flashy color and therefore easily detected.

To actually find out what is wrong about the license you will have to visit the commit itself by pressing RET while point is on that commit in the log.

The reason the signatures are not shown in the log buffer is that Magit usually displays each commit on a single line. Displaying each commits signature on multiple lines would mess that up.

The --show-signature argument can be selected in the log popup but it is not actually passed to git log. Instead %G? is added to the value of the --format= argument.

That (%G?) causes some letter to be printed for each commit and the code that parses the log output detects that letter and uses it to determine what face should be used to display the commit message summary. The faces are named ~magit-signature-.... By default commits with "unproblematic" signatures are displayed the same way as regular text (i.e. like the default` face), while other commits are displayed using some flashy color and therefore easily detected.

To actually find out what is wrong about the license you will have to visit the commit itself by pressing RET while point is on that commit in the log.

The reason the signatures are not shown in the log buffer is that Magit usually displays each commit on a single line. Displaying each commits signature on multiple lines would mess that up.

The --show-signature argument can be selected in the log popup but it is not actually passed to git log. Instead %G? is added to the value of the --format= argument.

That (%G?) causes some letter to be printed for each commit and the code that parses the log output detects that letter and uses it to determine what face should be used to display the commit message summary. The faces are named magit-signature-.... By default commits with "unproblematic" signatures are displayed the same way as regular text (i.e. like the default face), while other commits are displayed using some flashy color and therefore easily detected.

To actually find out what is wrong about the license you will have to visit the commit itself by pressing RET while point is on that commit in the log.

The reason the signatures are not shown in the log buffer is that Magit usually displays each commit on a single line. Displaying each commits signature on multiple lines would mess that up.

Source Link
tarsius
  • 26.3k
  • 4
  • 74
  • 111
Loading