From: Sverre Rabbelier <srabbelier@gmail.com>
To: Miles Bader <miles@gnu.org>, Junio C Hamano <gitster@pobox.com>
Cc: Nicolas Sebrecht <nicolas.s.dev@gmx.fr>,
Maxim Treskin <zerthurd@gmail.com>,
git@vger.kernel.org
Subject: Re: FEATURE REQUEST: Comment assignment on branches
Date: Tue, 16 Mar 2010 07:26:26 +0100 [thread overview]
Message-ID: <fabb9a1e1003152326m4d67f48bkc207ba7368cb54e4@mail.gmail.com> (raw)
In-Reply-To: <fc339e4a1003152320i12a7d4b2p711f6b5d0eda9bcd@mail.gmail.com>
Heya,
On Tue, Mar 16, 2010 at 07:20, Miles Bader <miles@gnu.org> wrote:
> On Tue, Mar 16, 2010 at 3:03 PM, Junio C Hamano <gitster@pobox.com> wrote:
>> If you mean by "publicly visible" branches in public repositories, I
>> suspect not. At places like repo.or.cz, github, or installations managed
>> by gitosis, you typically do not have direct access to $GIT_DIR/config
>> files (they belong to site administrators) in your repositories, and that
>> is not likely to change for security reasons.
>
> Hm, ok you're right... which is a shame... :(
Which is also why I think it would be nice if we could teach notes to
annotate branches/tags/the whole shaboodle. I really think that a
generic way to annotate something under /refs/ would be useful.
--
Cheers,
Sverre Rabbelier
next prev parent reply other threads:[~2010-03-16 6:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-15 8:33 FEATURE REQUEST: Comment assignment on branches Maxim Treskin
2010-03-15 21:10 ` René Scharfe
2010-03-15 21:32 ` Junio C Hamano
2010-03-16 0:35 ` Mark Lodato
2010-03-16 1:49 ` Junio C Hamano
2010-03-16 14:36 ` Nguyen Thai Ngoc Duy
2010-03-15 21:32 ` Nicolas Sebrecht
2010-03-15 21:34 ` Junio C Hamano
2010-03-16 4:45 ` Miles Bader
2010-03-16 6:03 ` Junio C Hamano
2010-03-16 6:20 ` Miles Bader
2010-03-16 6:26 ` Sverre Rabbelier [this message]
2010-03-16 7:33 ` 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=fabb9a1e1003152326m4d67f48bkc207ba7368cb54e4@mail.gmail.com \
--to=srabbelier@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=miles@gnu.org \
--cc=nicolas.s.dev@gmx.fr \
--cc=zerthurd@gmail.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).