Re: Does anyone use git-notes?
- From
- Tor Arntsen <tor@spacetec.no>
- Date
- Aug 26, 2010, 07:56 UTC
- Message-ID
- <AANLkTim01==of5ce07F4MFVazevNiRQLBMv38ferSgKB@mail.gmail.com>
- In-Reply-To
- <AANLkTin=VXp2BU0vhTLUy6MpJ7spXRs1dZC1wygoN6T-@mail.gmail.com>
On Wed, Aug 25, 2010 at 20:15, Scott Chacon <schacon@gmail.com> wrote:
Show 6 quoted lines
> I would like to write a post on how to use them, but I'm a bit > confused as to how people actually use them on a day to day basis. I > appears to me in trying to work out a flow for them that the lack of > an ability to merge them makes them very difficult to use for anything > practical. Can someone share with me how they use them and what the > cycle is?
I use Notes in a very simplistic way. For example, with an emulator I'm writing I have two or three ways of using git-notes: 1: I commit fixes and changes with a commit message describing the fix. Later I may find out that the fix made a couple more programs of the set I have run in the emulator, so I add a note to the commit saying 'This change makes X and Y work'. 2: I add test cases to the instruction validator I wrote for the emulator, if the test currently fails I say so in the commit message. At some later point I may commit a fix that lets the test pass, then I go back to the original commit message (which said the test currently failed) and add a note saying 'Fixed by [commit] nnnnnnn'. 3: Occasionally I just use notes as a reminder. If a commit adds a new feature I may later (after using the feature) add a 'todo'-note about what improvements I should add.
One use case I have thought of for the company case is to add notes to a release commit with information that wasn't or couldn't be added at the time of the commit, e.g. a list of problem reports closed by the release. But I haven't actually figured out how I can get Notes transferred over a pull yet.. although I haven't tried since 1.7.0.
-Tor