Re: Storing additional information in commit headers
- From
Martin Langhoff <martin.langhoff@gmail.com>
- Date
- Aug 1, 2011, 19:33 UTC
- Message-ID
- <CACPiFCLPgsC+9cX7r33oCQ2AnuRXMTqOAE5RZLS7hXdHc6B-9Q@mail.gmail.com>
- In-Reply-To
- <20110801182845.GA4303@fishbowl.rw.madduck.net>
On Mon, Aug 1, 2011 at 2:28 PM, martin f krafft <madduck@madduck.net> wrote:
> For lack of a better idea (cf. [0]), I am currently toying with the > following approach:
Hi Martin!
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.
Speculation: you mention distro packaging, so I assume you're improving the Debian packaging integration, with git tracking debian/rules, perhaps with a wrapper. If you are using a wrapper program, it is trivial to update this "metadata" file, or to ensure it's valid/sane, in the preparations to commit, perhaps ensuring that a pre-commit-hook script is in place and executable.
hth,
m
-- martin.langhoff@gmail.com martin@laptop.org -- Software Architect - OLPC - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff