From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] split notes [was: Re: What's cooking in git.git (Jan 2009, #05; Wed, 21)]
Date: Sun, 01 Feb 2009 13:01:55 +0100 [thread overview]
Message-ID: <gm42vk$lg7$1@ger.gmane.org> (raw)
In-Reply-To: 1233455960.17688.122.camel@maia.lan
Sam Vilain wrote:
> test -z "$GIT_NOTES_REF" && GIT_NOTES_REF="$(git config core.notesref)"
> test -z "$GIT_NOTES_REF" && GIT_NOTES_REF="refs/notes/commits"
GIT_NOTES_REF=$($(GIT_NOTES_REF:-$(git config core.notesref):-refs/notes/commits)
Or something like that.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2009-02-01 12:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-22 3:55 What's cooking in git.git (Jan 2009, #05; Wed, 21) Junio C Hamano
2009-01-22 4:26 ` Jeff King
2009-01-22 5:57 ` [PATCH v2 1/5] Windows: Fix signal numbers Jeff King
2009-01-22 5:59 ` [PATCH v2 2/5] diff: refactor tempfile cleanup handling Jeff King
2009-01-22 6:02 ` [PATCH v2 3/5] chain kill signals for cleanup functions Jeff King
2009-01-30 7:55 ` Jeff King
2009-01-30 8:13 ` Johannes Sixt
2009-01-30 8:21 ` Jeff King
2009-01-31 0:28 ` Junio C Hamano
2009-01-31 1:44 ` Jeff King
2009-01-31 6:50 ` Jeff King
2009-02-01 1:58 ` Junio C Hamano
2009-01-22 6:03 ` [PATCH v2 4/5] refactor signal handling " Jeff King
2009-01-22 6:03 ` [PATCH v2 5/5] pager: do wait_for_pager on signal death Jeff King
2009-01-22 5:13 ` What's cooking in git.git (Jan 2009, #05; Wed, 21) Johannes Schindelin
2009-01-31 6:45 ` Sam Vilain
2009-01-31 7:36 ` Jeff King
2009-02-01 2:39 ` [PATCH] split notes [was: Re: What's cooking in git.git (Jan 2009, #05; Wed, 21)] Sam Vilain
2009-02-01 3:09 ` Sam Vilain
2009-02-01 12:01 ` Jakub Narebski [this message]
2009-01-22 5:21 ` What's cooking in git.git (Jan 2009, #05; Wed, 21) Boyd Stephen Smith Jr.
2009-01-23 6:23 ` Junio C Hamano
2009-01-27 1:43 ` Boyd Stephen Smith Jr.
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='gm42vk$lg7$1@ger.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.