Git development
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: David Reiss <dreiss@facebook.com>, git@vger.kernel.org
Subject: Re: [PATCH v3] Add support for GIT_CEILING_DIRS
Date: Thu, 15 May 2008 21:34:24 +0100 (BST)	[thread overview]
Message-ID: <alpine.DEB.1.00.0805152131390.30431@racer> (raw)
In-Reply-To: <7vej83gxjm.fsf@gitster.siamese.dyndns.org>

Hi,

On Thu, 15 May 2008, Junio C Hamano wrote:

> David Reiss <dreiss@facebook.com> writes:
> 
> > + * ....  Paths must
> > + * be in a canonical form: empty components, or "." or ".." components
> > + * are not allowed.  prefix_list may be null, which is like "".
> 
> The caller starts from cwd[] and chomps, so you can safely assume that 
> it would not feed anything problematic.  But prefix_list comes from 
> user's environment, and it is easy to make mistakes like doubled slashes 
> (which you seem to take care) and also is tempting to use ".." when 
> specifying the ceiling (e.g. "CEIL=$HOME/..").  Perhaps canonicalizing 
> the ceiling would make this easier to use for end users?

Is this not going too far?  I mean, CEILING_DIRECTORIES is already a very 
special case.

> How well would this colon separated list work with msys folks?

Not well at all.  At least for the moment, I think setting this variable 
would fail (since it would be rewritten into a Windows-PATH-style string).  
Though honestly, I have no idea what getcwd() does on MinGW.

Steffen is working on that rewriting stuff, so maybe it will be a 
non-issue, eventually.

Ciao,
Dscho

  reply	other threads:[~2008-05-15 20:35 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-15 18:49 [PATCH v3] Add support for GIT_CEILING_DIRS David Reiss
2008-05-15 19:03 ` Johannes Schindelin
2008-05-15 19:40   ` David Reiss
2008-05-15 20:27   ` [PATCH] Add support for GIT_CEILING_DIRECTORIES Johannes Schindelin
2008-05-15 21:09     ` David Reiss
2008-05-15 22:29       ` Johannes Schindelin
2008-05-15 22:45         ` David Reiss
2008-05-15 23:27           ` [SQUASHED PATCH] " Johannes Schindelin
2008-05-16  6:54             ` Johannes Sixt
2008-05-16 10:20               ` Johannes Schindelin
2008-05-16 10:50                 ` Johannes Sixt
2008-05-16 17:43                   ` David Reiss
2008-05-17  0:19                     ` Johannes Schindelin
2008-05-17  0:20                       ` [2nd SQUASHED " Johannes Schindelin
2008-05-19  7:55                       ` [SQUASHED " Johannes Sixt
2008-05-19 10:49                         ` Johannes Schindelin
2008-05-15 19:46 ` [PATCH v3] Add support for GIT_CEILING_DIRS Junio C Hamano
2008-05-15 20:34   ` Johannes Schindelin [this message]
2008-05-16  7:03     ` Johannes Sixt
2008-05-16 10:21       ` 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=alpine.DEB.1.00.0805152131390.30431@racer \
    --to=johannes.schindelin@gmx.de \
    --cc=dreiss@facebook.com \
    --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