# 
# 
# patch "notes/release-checklist.txt"
#  from [9780239bd39e5c648a9bec70e4bb2ece9d232182]
#    to [878225c265c8950aa58fce3c936b8fef39990d23]
# 
============================================================
--- notes/release-checklist.txt	9780239bd39e5c648a9bec70e4bb2ece9d232182
+++ notes/release-checklist.txt	878225c265c8950aa58fce3c936b8fef39990d23
@@ -9,17 +9,10 @@
    mention any incompatibilities at the top, and generally it's a good
    idea to put cool new stuff above nice-but-not-as-exciting stuff.
 
-   A useful command (don't forget to substitute the correct value for
-   "<LAST-RELEASE>"):
+   A useful command:
 
-     $ mtn automate ancestry_difference \
-         $(mtn automate select h:net.venge.monotone) \
-         $(mtn automate select t:monotone-<LAST-RELEASE>) \
-       | mtn automate toposort address@hidden \
-       | xargs -n1 mtn log --last=1 -r
+     $ mtn log -r h:net.venge.monotone --to t:monotone-*
 
-   (The length of the previous line should be considered a mtn bug.)
-
    Commit your release notes, so other people can see them.
 
 1.5) Get people to read over your release notes, it's really easy to