git.madduck.net Git - code/vcsh.git/commit

Every one of the projects in this repository is available at the canonical URL git://git.madduck.net/madduck/pub/<projectpath> — see each project's metadata for the exact URL.

All patches and comments are welcome. Please squash your changes to logical commits before using git-format-patch and git-send-email to patches@git.madduck.net. If you'd read over the Git project's submission guidelines and adhered to them, I'd be especially grateful.

If you use my repositories frequently, consider adding the following snippet to ~/.gitconfig and using the third clone URL listed for each project:

author	martin f. krafft <madduck@madduck.net>
	Sat, 27 Apr 2013 06:17:30 +0000 (08:17 +0200)
committer	martin f. krafft <madduck@madduck.net>
	Fri, 19 Jul 2013 17:20:35 +0000 (19:20 +0200)
commit	e9a6b438443bad91e92032fbb9923aa3ebd5bb5b
tree	4509a3807dc620471928e61d08904dc98b407eb8	tree \| snapshot
parent	84568765dd14a56d66a3b0dcf6ff72d3aaa71a7f	commit \| diff

Keep worktree relative to GIT_DIR

core.worktree can be set relatively to GIT_DIR, thereby preventing the
hard-coding of the home directory path, which should make a vcsh setup
more portable.

On the other hand, this means that the vcsh repo.d is now invariably
linked to its position, relative to the base directory. Apply this patch
only if you think it to be less likely that people change
~/.config/vcsh/repo.d to something else, than they would rsync/tar/mv
a whole tree to a different $HOME.

Paths are resolved using Git itself, for maximum portability.

In addition to making sure the new method works on new repositories,
I checked that

- "old" repositories can be used with the new code just fine;
- upgrading works.

Signed-off-by: martin f. krafft <madduck@madduck.net>

madduck's git repository

Legalese