also sprach Martin Langhoff <martin.langhoff@xxxxxxxxx> [2011.08.01.2133 +0200]: > What data are you trying to include? Some time ago, I had similar > ideas to yours for a while... and it ended up being that all I needed > was to put the additional data /in a file/ and commit that file. Hi, thanks for taking the time to reply to me! I am trying to store the top-base of a TopGit branch, which is the merge of all a branch's dependencies. TopGit uses refs for that, but a ref can only ever point at one such merge, and so it's hard-to-impossible to reconstruct a branch dependency in the past. TopGit does use files in the worktree too. I would love to get rid of this as well, since a file like .topmsg (which differs between all branches, even related ones), requires to always remember to use the 'ours' merge driver, which requires setup, which makes it harder to use. > If you are using a wrapper program, I am trying to stay as close as possible to plain Git. All of this could easily be done by a wrapper, but a wrapper always makes too many assumptions to become a viable standard for Debian packaging. > it's valid/sane, in the preparations to commit, perhaps ensuring > that a pre-commit-hook script is in place and executable. Again, that requires setup, which increases the barrier of entry to passerby's and new contributors. -- martin | http://madduck.net/ | http://two.sentenc.es/ "verbing weirds language." -- calvin spamtraps: madduck.bogus@xxxxxxxxxxx
Attachment:
digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)