git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Sitaram Chamarty <sitaramc@gmail.com>
To: git@vger.kernel.org
Subject: Re: How to find out which gitignore blocks my git-add
Date: Sat, 7 Feb 2009 12:44:27 +0000 (UTC)	[thread overview]
Message-ID: <slrngor0hb.cq.sitaramc@sitaramc.homelinux.net> (raw)
In-Reply-To: 20090207064221.GA14856@coredump.intra.peff.net

On 2009-02-07, Jeff King <peff@peff.net> wrote:
> A toy patch series follows; see 2/2 for a description of why it doesn't
> work like you might hope. I'm not too interested in trying to deal with
> the refactoring that would be required to do it right. But maybe
> somebody else is.

I was thinking it could simply be a separate utility in
contrib for starters, perhaps not even written in C.  I
don't mind volunteering to write one in shell+the usual
toolchain (and I'll test it on msysgit too, because I have
Windows users).  My C days are a bit behind me, sadly...

  parent reply	other threads:[~2009-02-07 12:47 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-06  9:38 How to find out which gitignore blocks my git-add Gonzo
2009-02-06 19:33 ` Jeff King
2009-02-07  1:33   ` Sitaram Chamarty
2009-02-07  6:42     ` Jeff King
2009-02-07  6:44       ` [PATCH 1/2] refactor exclude handling Jeff King
2009-02-07  6:44       ` [PATCH 2/2] give exclude mechanism a debug option Jeff King
2009-02-07  7:38         ` Junio C Hamano
2009-02-07  7:42           ` Junio C Hamano
2009-02-07 11:46             ` Jeff King
2009-02-07 11:44           ` Jeff King
2009-02-07 21:45             ` Junio C Hamano
2009-02-08  8:59               ` Jeff King
2009-02-08  9:50                 ` Junio C Hamano
2009-02-08  9:52                   ` Jeff King
2009-02-07 12:44       ` Sitaram Chamarty [this message]
2009-02-07 13:31         ` How to find out which gitignore blocks my git-add Jeff King
2009-02-06 22:00 ` Bisani, Alok

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=slrngor0hb.cq.sitaramc@sitaramc.homelinux.net \
    --to=sitaramc@gmail.com \
    --cc=git@vger.kernel.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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).