From: "Alex Riesen" <raa.lkml@gmail.com>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: "Nicolas Pitre" <nico@cam.org>,
"Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
git@vger.kernel.org, "Johan Herland" <johan@herland.net>
Subject: Re: [PATCH] Introduce light weight commit annotations
Date: Mon, 11 Jun 2007 10:05:53 +0200 [thread overview]
Message-ID: <81b0412b0706110105t369d908v70a140505caee778@mail.gmail.com> (raw)
In-Reply-To: <7vbqfnrl54.fsf@assigned-by-dhcp.pobox.com>
On 6/11/07, Junio C Hamano <gitster@pobox.com> wrote:
> "Alex Riesen" <raa.lkml@gmail.com> writes:
>
> > It is still a reference, really. Besides, if it is not under refs/, we'd
> > have to change fetch/push to allow distribution of the notes/annotations
> > (there are special assumptions regarding reference names starting
> > with "refs/"). Right now it just works.
>
> Two issues.
>
> One is that it is unclear is how the reachability rules should
> be. Should an ??/?{38} entry in the refs/annotations/commits
> protects the commit the entry talks about (i.e. ???{38}) from
> getting pruned?
I think it should be the other way around: annotations get loose
and reported as such (and maybe even removed) by git-fsck.
next prev parent reply other threads:[~2007-06-11 8:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-09 17:55 [PATCH] Introduce light weight commit annotations Johannes Schindelin
2007-06-10 13:14 ` Johan Herland
2007-06-10 18:56 ` Johannes Schindelin
2007-06-10 19:20 ` Johan Herland
2007-06-10 19:53 ` Johannes Schindelin
2007-06-10 22:11 ` Junio C Hamano
2007-06-10 23:00 ` Johannes Schindelin
2007-06-10 23:29 ` Junio C Hamano
2007-06-11 10:25 ` Johannes Schindelin
2007-06-12 17:28 ` Johannes Schindelin
2007-06-10 22:58 ` Alex Riesen
2007-06-10 23:20 ` Alex Riesen
2007-06-11 1:11 ` Junio C Hamano
2007-06-11 2:09 ` Nicolas Pitre
2007-06-11 7:24 ` Alex Riesen
2007-06-11 7:43 ` Junio C Hamano
2007-06-11 8:05 ` Alex Riesen [this message]
2007-06-11 10:22 ` 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=81b0412b0706110105t369d908v70a140505caee778@mail.gmail.com \
--to=raa.lkml@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=johan@herland.net \
--cc=nico@cam.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).