Git development
 help / color / mirror / Atom feed
From: Alex Riesen <raa.lkml@gmail.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: allow only a strictly defined set of references under .git/
Date: Fri, 16 Dec 2005 21:44:27 +0100	[thread overview]
Message-ID: <20051216204427.GA4164@steel.home> (raw)
In-Reply-To: <7v1x0cj4zz.fsf@assigned-by-dhcp.cox.net>

Junio C Hamano, Fri, Dec 16, 2005 19:01:20 +0100:
> > Maybe we should only allow only a strictly defined set of refnames
> > under $GIT_DIR? The directory is used pretty much for anything else
> > (temporary message files, config, description).
> 
> I am glad somebody is paying attention.
> 

I actually run into it...

> Probably post 1.0 --- I have not assessed the extent of
> confusion yet.

It has good chances to continue to grow, as git gets more exposure.

      reply	other threads:[~2005-12-16 20:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-16  8:24 allow only a strictly defined set of references under .git/ Alex Riesen
2005-12-16 18:01 ` Junio C Hamano
2005-12-16 20:44   ` Alex Riesen [this message]

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=20051216204427.GA4164@steel.home \
    --to=raa.lkml@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    /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