git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johan Herland <johan@herland.net>
To: git@vger.kernel.org
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Jakub Narebski <jnareb@gmail.com>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Commit annotations (was:: Octopus merge: unique (?) to git, but is it useful?)
Date: Wed, 04 Jun 2008 01:59:28 +0200	[thread overview]
Message-ID: <200806040159.28603.johan@herland.net> (raw)
In-Reply-To: <alpine.DEB.1.00.0806032131300.13507@racer.site.net>

On Tuesday 03 June 2008, Johannes Schindelin wrote:
> On Tue, 3 Jun 2008, Jakub Narebski wrote:
> > By the way, what is status of git-notes / commit annotations?  Did it
> > got abandoned, on hiatus, or what?
> 
> You probably meant to Cc: me, and Linus, right?
> 
> I all but abandoned it.  It works, but I do not need it, and kind of 
> waited for the guy who wanted them to chime in, so that I did not waste my 
> time in vain.
> 
> IIRC it was Johan Herland, but I could be wrong.

Yes, I made the first (severely misguided) implementations [1][2] which
prompted Dscho to create an alternative implementation [3]. Although Dscho's
design was certainly more Git-esque than mine (keeping the notes in a
(pseudo)branch instead of creating a totally separate infrastructure for
note storage), at some point his efforts stalled (due to a combination of
scalability problems and/or lack of interest, IIRC).

I was happy to see some of this work recently resumed by Geoffrey Irving
[4].

(Side note: It is funny how Geoffrey's patch-id cache can be seen as yet
another instance of the reverse-mapping softref mechanism I proposed as
part of the first git-notes implementation [5])

>From the initial interest in git-notes, and the sporadic requests that have
been posted since its first mention, it seems that git-notes would be a
useful feature for many Git users. However, neither me nor Dscho have the
time/interest to keep pushing it. Maybe it's time for someone else to pick
up the torch?


Have fun! :)

...Johan


[1]: http://thread.gmane.org/gmane.comp.version-control.git/46770/focus=48540
[2]: http://thread.gmane.org/gmane.comp.version-control.git/49052
[3]: http://thread.gmane.org/gmane.comp.version-control.git/52598
[4]: http://thread.gmane.org/gmane.comp.version-control.git/83484
[5]: http://thread.gmane.org/gmane.comp.version-control.git/49052/focus=49592

-- 
Johan Herland, <johan@herland.net>
www.herland.net

  reply	other threads:[~2008-06-04  0:00 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-03  1:14 Octopus merge: unique (?) to git, but is it useful? Jakub Narebski
2008-06-03  2:05 ` Linus Torvalds
2008-06-03  3:56   ` Junio C Hamano
2008-06-03  5:17     ` Junio C Hamano
2008-06-03  5:28       ` Johannes Schindelin
2008-06-03  5:42         ` Junio C Hamano
2008-06-03  8:31           ` Johannes Schindelin
2008-06-03 10:40       ` SZEDER Gábor
2008-06-03 19:30         ` Junio C Hamano
2008-06-03 20:39           ` SZEDER Gábor
2008-06-03 22:08             ` Junio C Hamano
2008-06-03 23:10               ` SZEDER Gábor
2008-06-04  0:35                 ` Jeff King
2008-06-04  1:02                 ` Junio C Hamano
2008-06-03 14:40     ` Linus Torvalds
2008-06-03 23:11       ` Miklos Vajna
2008-06-04  0:33         ` Junio C Hamano
2008-06-03  4:29   ` Junio C Hamano
2008-06-03  6:39     ` Jakub Narebski
2008-06-03  7:11       ` Junio C Hamano
2008-06-03  7:32   ` Jakub Narebski
2008-06-03  7:53     ` Junio C Hamano
2008-06-03 19:54     ` Linus Torvalds
2008-06-03 20:27       ` Commit annotations (was:: Octopus merge: unique (?) to git, but is it useful?) Jakub Narebski
2008-06-03 20:33         ` Johannes Schindelin
2008-06-03 23:59           ` Johan Herland [this message]
2008-06-03  2:16 ` Octopus merge: unique (?) to git, but is it useful? Daniel Villeneuve
2008-06-03 10:06 ` Matthieu Moy
2008-06-03 11:27   ` Jakub Narebski
2008-06-03 11:53     ` Matthieu Moy

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=200806040159.28603.johan@herland.net \
    --to=johan@herland.net \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=torvalds@linux-foundation.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 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).