From: Dennis Kaarsemaker <dennis@kaarsemaker.net>
To: Marc Haber <mh+git@zugschlus.de>, git@vger.kernel.org
Subject: Re: how to check for uncommitted/unstaged changes on remote side before pushing
Date: Mon, 09 Nov 2015 10:38:20 +0100 [thread overview]
Message-ID: <1447061900.5074.12.camel@kaarsemaker.net> (raw)
In-Reply-To: <20151109093124.GB18762@torres.zugschlus.de>
On ma, 2015-11-09 at 10:31 +0100, Marc Haber wrote:
> Abusing git here has the advantage that one can save local changes
> and merge them, which is handy for the task at hand (which is
> deploying my dotfiles to "my" servers).
For this I really like vcsh (https://github.com/RichiH/vcsh/) in
combination with a .bashrc.d snippet that updates dotfiles upon login
when possible (
https://github.com/seveas/dotfiles/blob/master/.bashrc.d/vcsh.sh)
--
Dennis Kaarsemaker
www.kaarsemaker.net
prev parent reply other threads:[~2015-11-09 9:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-08 21:23 how to check for uncommitted/unstaged changes on remote side before pushing Marc Haber
2015-11-09 8:25 ` Dennis Kaarsemaker
2015-11-09 9:31 ` Marc Haber
2015-11-09 9:38 ` Dennis Kaarsemaker [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1447061900.5074.12.camel@kaarsemaker.net \
--to=dennis@kaarsemaker.net \
--cc=git@vger.kernel.org \
--cc=mh+git@zugschlus.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).