git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tor Arntsen <tor@spacetec.no>
To: Scott Chacon <schacon@gmail.com>
Cc: git list <git@vger.kernel.org>
Subject: Re: Does anyone use git-notes?
Date: Thu, 26 Aug 2010 09:56:55 +0200	[thread overview]
Message-ID: <AANLkTim01==of5ce07F4MFVazevNiRQLBMv38ferSgKB@mail.gmail.com> (raw)
In-Reply-To: <AANLkTin=VXp2BU0vhTLUy6MpJ7spXRs1dZC1wygoN6T-@mail.gmail.com>

On Wed, Aug 25, 2010 at 20:15, Scott Chacon <schacon@gmail.com> wrote:
> 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

  parent reply	other threads:[~2010-08-26  7:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-25 18:15 Does anyone use git-notes? Scott Chacon
2010-08-25 18:40 ` Joshua Jensen
2010-08-25 18:52 ` Thomas Rast
2010-08-25 22:42 ` Junio C Hamano
2010-08-25 22:43 ` Junio C Hamano
2010-08-26  7:56 ` Tor Arntsen [this message]
2010-08-26  8:09 ` Michael J Gruber
2010-08-26 13:09   ` Will Palmer
2010-08-26  8:26 ` Jon Seymour

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='AANLkTim01==of5ce07F4MFVazevNiRQLBMv38ferSgKB@mail.gmail.com' \
    --to=tor@spacetec.no \
    --cc=git@vger.kernel.org \
    --cc=schacon@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).