[PATCH] git push pull

Saeed Rasooli saeed.gnu at gmail.com
Sun Jan 6 16:11:07 CET 2019

I disagree with auto-push too (unless enabled explicitly with an
environment variable). For example if the remote git repo is encrypted on
server-side (something like git-remote-gcrypt), then git push becomes slow.
You may even want to push to a local storage device that is not always
plugged in. Or you are keeping your passwords in another bigger repo along
with some other things you want to synchronize. There are many more cases
that you don't want to have auto-push (or maybe even auto-commit).
Afterall this is Linux, and we never want to loose the flexibility of Linux.

On Sun, Jan 6, 2019, 5:36 PM Tinu Weber <takeya at bluewin.ch wrote:

> On Sat, Jan 05, 2019 at 21:24:10 -0800, Pass Word wrote:
> > This patch adds git pull before commit and push after if a remote exists.
> The main appeal of pass for me is that it keeps things relatively
> simple. And for me "simple" means: I don't expect a `git commit` to
> automagically interact with a remote; these are two distinct things that
> should IMHO not be mixed up.
> If anything, I would make this optional at least.
> Best,
> Tinu
> _______________________________________________
> Password-Store mailing list
> Password-Store at lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/password-store
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.zx2c4.com/pipermail/password-store/attachments/20190106/a0c88e96/attachment.html>

More information about the Password-Store mailing list