The revocation string occurs on a new line and does not exactly
indicate which key was revoked due to the use of the word "This". It
requires that you parse a few lines before you determine that "This"
refers to the key that is presented on the following line.

For example:

Command> list
pub 4096R/DEADBEEF created: 2007-06-02 expires: 2011-06-02 usage: SC
trust: ultimate validity: ultimate
sub 4096R/DEADBEEG created: 2007-06-02 expires: 2011-06-02 usage: E
sub 2048R/DEADBEEE created: 2008-10-05 expires: never usage: A
This key was revoked on 2010-06-02 by RSA key DEADBEEF Dead Beef Man <dead@beef.org>
sub 4096R/DEADBEED created: 2010-06-02 revoked: 2010-06-02 usage: E
This key was revoked on 2010-06-02 by RSA key DEADBEEF Dead Beef Man <dead@beef.org>
sub 4096R/DEADBEEC created: 2010-06-02 revoked: 2010-06-02 usage: E

With some careful reading you can eventually deduce that the "This
key" line is before the key that is revoked.

To increase the user's interface with the output of the tool, I would
suggest a minor modification to the language to provide clarification
which key is being discussed, for example:

The following key was revoked on 2010-06-02 by RSA key DEADBEEF Dead Beef Man
<dead@beef.org>

If the list presented in an --edit-key 'list' operation is not always
going to be the same order in every case, then I would suggest instead
that the language indicate exactly what key was revoked by including
the keyid, like the following:

Key DEADBEED was revoked on 2010-06-02 by RSA key DEADBEEF Dead Beef Man
<dead@beef.org>

thanks! I think this minor tweak would help improve the user interface
of gpg.