Re: File versioning based on shallow Git repositories?

Would initiating a repo with a empty root commit, tag it with 'base' then use $ git rebase --onto base master@{30 days ago} master; be viable? The --orphan & tag is perhaps more robust, since it's "harder" to move tags around. -- Rafael Ascensão

Re: How to undo previously set configuration?

On Fri, Apr 6, 2018 at 4:55 PM, Olaf Hering wrote: > > This does not work. Initially I copied the global config into the repo and > set all unwanted values to , like 'smtpuser='. Perhaps the config > parser recognized that fact, but the consumer does not? > Today someone asked

git complains packed-refs is not a directory when used with GIT_DIR and GIT_WORK_TREE envvars.

One of the tools that manages PKGBUILDS for Arch Linux stores PKGBUILD git repos inside a cache directory for reuse. One of the repos is triggering some unexpected behaviour that can be reproduced in the CLI with: $ GIT_DIR=spotify/.git GIT_WORK_TREE=spotify git reset HEAD fatal: couldn't

Re: [PATCH/RFC] git-post: the opposite of git-cherry-pick

> This is worth discussing, though not my preference. The picture to "pick > cherries" has become quite common, and now that we use it for the name of > the command, "cherry-pick", the direction of flow is quite obvious and > strongly implied: from somewhere else to me (and not to somebody else).