also sprach Sverre Rabbelier <srabbelier@xxxxxxxxx> [2011.08.01.2027 +0200]: > On Mon, Aug 1, 2011 at 20:20, martin f krafft <madduck@xxxxxxxxxxx> wrote: > > My intent was to add an extra commit header to select commits as > > a way to store extra information needed to automate the management > > of interdependent branches and patch generation à la TopGit. > > Have you had a look at git notes? Hello, and thanks for taking the time to reply to me! Yes, I have considered git-notes. The issue I have with git-notes is that it requires every contributor to set up refspecs for fetch and push, or else the notes will not be exchanged/shared. I realise this is a minor concern to most of you, or maybe even a feature (part of the beauty of Git is, after all, that it works without requiring everyone to have the same local setup), but in our use-case (distro packaging), it's a relatively large burden to new contributors and passerby's (sp?). Also, git-notes are mutable (at least from the UI perspectiv) and I strive to encode information immutably. Therefore I am looking for a means to encode this (necessary) information as part of the main DAG (i.e. not polluting the worktree). I hope this makes sense. -- martin | http://madduck.net/ | http://two.sentenc.es/ "first get your facts; then you can distort them at your leisure." -- mark twain spamtraps: madduck.bogus@xxxxxxxxxxx
Attachment:
digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)