From: Jeff King <peff@peff.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Dec 2008, #03; Sun, 21)
Date: Tue, 23 Dec 2008 11:38:13 -0500 [thread overview]
Message-ID: <20081223163811.GA25658@coredump.intra.peff.net> (raw)
In-Reply-To: <alpine.DEB.1.00.0812231725270.30769@pacific.mpi-cbg.de>
On Tue, Dec 23, 2008 at 05:26:01PM +0100, Johannes Schindelin wrote:
> > I haven't had much time to really look at this closely, and I probably
> > won't for another week or so due to the holidays. But from my cursory
> > examination, I think I want to propose something that is a bit
> > different.
>
> Could you be a bit more, like, specific, please?
The way that GIT_NOTES_REF and core.notesref work aren't what I had in
mind. I imagined something more amenable to having lots of different
metadata notes. Refer to the other messages I have written on "naming".
I don't want to hold up progress, so if people want those patches in
"next", then go for it. What I really meant by my email was that I think
my suggested changes might be simpler to see as a re-roll rather than
patches on top, but since I can't work on them for a while, I didn't
want Junio to take silence as "OK, nobody has complained, so it's time
for this to graduate to next." But again, if people are ready to start
playing with this and building on top of it, then I don't want to stand
in the way.
-Peff
next prev parent reply other threads:[~2008-12-23 16:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-21 12:23 What's cooking in git.git (Dec 2008, #03; Sun, 21) Junio C Hamano
2008-12-21 19:03 ` Jakub Narebski
2008-12-23 12:05 ` Jeff King
2008-12-23 16:26 ` Johannes Schindelin
2008-12-23 16:38 ` Jeff King [this message]
2008-12-23 16:52 ` Johannes Schindelin
2008-12-23 17:34 ` Jeff King
2008-12-24 11:55 ` Johannes Schindelin
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=20081223163811.GA25658@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).