From: Mike Hommey <mh@glandium•org>
To: Junio C Hamano <gitster@pobox•com>
Cc: git@vger•kernel.org
Subject: Re: What's cooking in git.git (Jan 2016, #02; Mon, 11)
Date: Tue, 12 Jan 2016 09:06:12 +0900 [thread overview]
Message-ID: <20160112000612.GA32363@glandium.org> (raw)
In-Reply-To: <xmqqlh7vvfxc.fsf@gitster.mtv.corp.google.com>
On Mon, Jan 11, 2016 at 03:45:35PM -0800, Junio C Hamano wrote:
> * mh/notes-allow-reading-treeish (2015-10-08) 3 commits
> (merged to 'next' on 2015-10-23 at 8a697f0)
> + notes: allow treeish expressions as notes ref
> + Merge branch 'jk/notes-dwim-doc' into next
> + Merge branch 'jc/merge-drop-old-syntax' into next
> (this branch uses jc/merge-drop-old-syntax.)
>
> Some "git notes" operations, e.g. "git log --notes=<note>", should
> be able to read notes from any tree-ish that is shaped like a notes
> tree, but the notes infrastructure required that the argument must
> be a ref under refs/notes/. Loosen it to require a valid ref only
> when the operation would update the notes (in which case we must
> have a place to store the updated notes tree, iow, a ref).
>
> As the patch was done on top of the 'drop old-syntax from merge',
> this has to wait until that other topic can graduate, unfortunately.
> It can be redone in a way that does not depend on that topic after
> this cycle, though.
I'm not sure what you mean here. The patch applies just fine on top of
current master.
Mike
next prev parent reply other threads:[~2016-01-12 0:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-11 23:45 What's cooking in git.git (Jan 2016, #02; Mon, 11) Junio C Hamano
2016-01-12 0:06 ` Mike Hommey [this message]
2016-01-12 3:04 ` Junio C Hamano
2016-01-12 4:34 ` Edmundo Carmona Antoranz
2016-01-12 8:39 ` Johannes Schindelin
2016-01-12 18:47 ` Junio C Hamano
2016-01-12 21:49 ` Jeff King
2016-01-13 23:07 ` Junio C Hamano
2016-01-13 23:22 ` Jeff King
2016-01-13 23:44 ` Junio C Hamano
2016-01-13 23:54 ` Junio C Hamano
2016-01-14 10:21 ` Jeff King
2016-01-13 2:56 ` David A. Greene
2016-01-18 13:35 ` Michael J Gruber
2016-01-18 17:06 ` Jeff King
2016-01-18 21:39 ` Eric Wong
2016-01-19 7:07 ` Michael J Gruber
2016-01-25 9:56 ` Duy Nguyen
2016-01-25 22:03 ` Junio C Hamano
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=20160112000612.GA32363@glandium.org \
--to=mh@glandium$(echo .)org \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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