git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: how to check for uncommitted/unstaged changes on remote side before pushing

From
Dennis Kaarsemaker <dennis@kaarsemaker.net>
Date
Nov 9, 2015, 09:38 UTC
Message-ID
<1447061900.5074.12.camel@kaarsemaker.net>
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
Previous: Marc Haber
Message 4 of 4 in “how to check for uncommitted/unstaged changes on remote side before pushing”
  1. Marc HaberNov 8, 2015
  2. Dennis KaarsemakerNov 9, 2015
  3. Marc HaberNov 9, 2015
  4. Dennis KaarsemakerNov 9, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.