aboutsummaryrefslogtreecommitdiff
path: root/bin/vpnsetup
diff options
context:
space:
mode:
authorMiquel Sabaté Solà <msabate@suse.com>2020-04-27 14:31:32 +0200
committerMiquel Sabaté Solà <msabate@suse.com>2020-04-27 14:31:32 +0200
commit22f7cfc806c9a47b3bde69e6c12da97f88e7c525 (patch)
treee463add5cee38d588a3eeaa771dea614514cf225 /bin/vpnsetup
parentb58bfcced96c9408cc5f92f37f488ae01199433b (diff)
downloaddotfiles-22f7cfc806c9a47b3bde69e6c12da97f88e7c525.tar.gz
dotfiles-22f7cfc806c9a47b3bde69e6c12da97f88e7c525.zip
emacs: turns out that magit can indeed stage by patches
Before knowing this I had to resort to the CLI and manually `git stash -p` all the way. Turns out that magit is actually able to stage particular changes from a specific files, so this whole workflow is no longer needed, and hence the warning on the documentation is no longer valid. Signed-off-by: Miquel Sabaté Solà <msabate@suse.com>
Diffstat (limited to 'bin/vpnsetup')
0 files changed, 0 insertions, 0 deletions