<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">On Mar 2, 2020, at 10:33 AM, Christian Weiss <<a href="mailto:news_001@washammwa.de" class="">news_001@washammwa.de</a>> wrote:<br class=""><div><blockquote type="cite" class=""><div class=""><div class="">So please make some suggestions of what text would help you when planing to revert to an earlyer commit.<br class="">I guess "Field X,Y,Z updated. Field M dropped, Field T added", is something that would help you, but for others this is maybe already to mutch details disclosed.<br class="">So maybe a .pass file with optional flags for the commit message generator is one way to implement it at password-store level.<br class=""></div></div></blockquote><div><br class=""></div><div>From what I read here, adding a command line option -e/--edit to open the editor with the specified message would suffice. I suggest -e/--edit because it is the git option to do the same.</div><div><br class=""></div><div>Pass could easily do the same for “git commit” --template and/or --message options.</div><br class=""><blockquote type="cite" class=""><div class=""><div class="">I guess a full revert of the whole repo e.g. 50 commits back to the past is not what you are looking for. I guess you are looking for restoring an old version of a specific password (file/path) - a re-commit of an older version of a password/file instead of a full rollback of the repo to a certain point in time (would result in loosing all other changes made to other passwords in between).<br class=""><br class="">I would like to see a "password-file history" in pass (only commits that belongs to that file, not all commits) within pass with the option to select one for restore (while leaving the file-history 100% complete).<br class="">Or are you asking for just good commit messages and doing it directly in git?<br class=""></div></div></blockquote><div><br class=""></div><div>The "git log” command does this already for a directory or a file, if you specify it. Like the --edit above, this could be a pass command (extension?) that makes “pass history <a href="http://example.com" class="">example.com</a>” a wrapper for “git log ~/.password-store/<a href="http://example.com" class="">example.com</a>”.</div><div><br class=""></div></div>jf<br class=""><div class="">
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant-ligatures: normal; font-variant-position: normal; font-variant-caps: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">-- </div><div class="">John Franklin</div><div class=""><a href="mailto:franklin@sentaidigital.com" class="">franklin@sentaidigital.com</a></div></div>
</div>
<br class=""></body></html>