zimfw/tools/zim_update

#
# zim_update - update the zim repository
#

cd ${ZDOTDIR:-${HOME}/.zim}

# this is the cleanest way I know how to update a repository
git remote update -p
git merge --ff-only @\{u\}
# and update the submodules
git submodule update --init --recursive

# return to previous directory after update
cd ~-
[tools] initial commit 2016-05-14 18:22:04 -04:00			`#`
			`# zim_update - update the zim repository`
			`#`

[meta] add module and fixup tools 2016-09-02 21:28:29 -04:00			`cd ${ZDOTDIR:-${HOME}/.zim}`
[tools] initial commit 2016-05-14 18:22:04 -04:00
[tools] zmanage update: track submodules This change causes `zmanage update` to track the submodules as described in origin/master, not from their upstream (dirty) states. Users wishing to "revert" this change on occasion to test some upstream submodule features, do: `cd ~/.zim && gSu`, assuming you have the git aliases. This will pull the upstream modules to their latest state, leaving a dirty HEAD state with these untracked modules. `cd ~/.zim && gSI` to revert. Closes #127 2017-01-21 11:25:30 -05:00			`# this is the cleanest way I know how to update a repository`
[tools] initial commit 2016-05-14 18:22:04 -04:00			`git remote update -p`
			`git merge --ff-only @\{u\}`
			`# and update the submodules`
[tools] zmanage update: track submodules This change causes `zmanage update` to track the submodules as described in origin/master, not from their upstream (dirty) states. Users wishing to "revert" this change on occasion to test some upstream submodule features, do: `cd ~/.zim && gSu`, assuming you have the git aliases. This will pull the upstream modules to their latest state, leaving a dirty HEAD state with these untracked modules. `cd ~/.zim && gSI` to revert. Closes #127 2017-01-21 11:25:30 -05:00			`git submodule update --init --recursive`
Circumvent directory change to .zim after zmanage update 2017-03-26 04:53:56 -04:00
			`# return to previous directory after update`
			`cd ~-`