zimfw/tools/zim_update

#
# zim_update - update the zim repository
#

cd ${ZIM_HOME}

# 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
[tools] initial commit 2016-05-14 15:22:04 -07:00			`#`
			`# zim_update - update the zim repository`
			`#`

Allow arbitrary ZIM location with ZIM_HOME This change allow arbitrary Zim location path by setting a new environment variable, ZIM_HOME. If the user does not set it, Zim falls back to the old "${ZDOTDIR:-${HOME}}/.zim" location. Closes #203 2017-06-10 20:54:22 -03:00			`cd ${ZIM_HOME}`
[tools] initial commit 2016-05-14 15:22:04 -07: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 08:25:30 -08:00			`# this is the cleanest way I know how to update a repository`
[tools] initial commit 2016-05-14 15:22:04 -07: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 08:25:30 -08:00			`git submodule update --init --recursive`
No results found.