git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jean-Philippe Gariépy" <jean-philippe.gariepy@nuecho.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: git@vger.kernel.org, Shawn Bohrer <shawn.bohrer@gmail.com>
Subject: Re: [BUG] git clean -X behaviour when .gitignore has sub-directory entries
Date: Sun, 03 Oct 2010 14:55:48 -0400	[thread overview]
Message-ID: <4CA8D1B4.1020801@nuecho.com> (raw)
In-Reply-To: <20100927203652.GB11957@burratino>

  On 09/27/2010 04:36 PM, Jonathan Nieder wrote:
> ...
>   1) a/b/f is not actually considered excluded; only its containing
>      directory is.
>
>   2) git clean does not even examine a/b to consider whether to remove
>      it: since a/ does not contain any tracked files, it stopped there.

Ok, thanks for your analysis.  Do you consider it a bug?



-- 
Jean-Philippe

  reply	other threads:[~2010-10-03 18:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-27 14:35 [BUG] git clean -X behaviour when .gitignore has sub-directory entries Jean-Philippe Gariépy
2010-09-27 20:36 ` Jonathan Nieder
2010-10-03 18:55   ` Jean-Philippe Gariépy [this message]
2010-10-03 19:12     ` Jonathan Nieder

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=4CA8D1B4.1020801@nuecho.com \
    --to=jean-philippe.gariepy@nuecho.com \
    --cc=git@vger.kernel.org \
    --cc=jrnieder@gmail.com \
    --cc=shawn.bohrer@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).