git-wad

Manage files via git but not their content
git clone git://git.meso-star.fr/git-wad.git
Log | Files | Refs | README | LICENSE

commit 7c0fa84fb010bb73397cc45bb085451908717ecc
parent 07aa68c6cf43fd42c5f92510df95782334756c3b
Author: Vincent Forest <vincent.forest@meso-star.com>
Date:   Sat, 16 Mar 2024 18:49:04 +0100

Make certain internal variables constant

It seems pointless to let the user define variables other than those
used to configure repository URIs. For example, changing the
GIT_WAD_HEADER would make the identification of WAD files dependent on
the user's configuration, which could even change over time. Worse
still, this could be dangerous. Changing the GIT_WAD_OBJDIR variable
could result in the deletion of files that should not be deleted when
the prune subcommand is executed.

Diffstat:
Mgit-wad | 7++++---
1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/git-wad b/git-wad @@ -25,10 +25,11 @@ if [ -f "${config_file}" ]; then . "${config_file}" fi +GIT_WAD_HEADER="#\$# git-wad" +GIT_WAD_OBJDIR=".git/wad" +GIT_WAD_VERBOSE=1 + # Default options -[ -z "${GIT_WAD_HEADER}" ] && GIT_WAD_HEADER="#\$# git-wad" -[ -z "${GIT_WAD_OBJDIR}" ] && GIT_WAD_OBJDIR=".git/wad" -[ -z "${GIT_WAD_VERBOSE}" ] && GIT_WAD_VERBOSE=1 [ -z "${GIT_WAD_REMOTE_PUSH}" ] && GIT_WAD_REMOTE_PUSH="" [ -z "${GIT_WAD_REMOTE_FETCH}" ] && GIT_WAD_REMOTE_FETCH="${GIT_WAD_REMOTE_PUSH}"