git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
To: rpjday@crashcourse.ca, git@vger.kernel.org
Subject: Re: is there a truly compelling rationale for .git/info/exclude?
Date: Fri, 06 Oct 2017 19:48:44 +0530	[thread overview]
Message-ID: <1507299524.12554.9.camel@gmail.com> (raw)
In-Reply-To: <20171006061434.Horde.16MqZ-fejqXm6BLpL7prK1K@crashcourse.ca>

On Fri, 2017-10-06 at 06:14 -0400, rpjday@crashcourse.ca wrote:
>    and in this funny grey area in between, we have .git/info/exclude,
> to be used for ... what, exactly? the one argument i've come up with
> is the situation where you discover that a repo you've cloned has an
> incomplete set of .gitignore patterns, and while you submit a patch
> for that to the maintainer, you can temporarily add that pattern
> to .git/info/exclude, and as soon as the patch is accepted, you can
> toss it.
> 
>    but even that isn't a really compelling reason. so what's it for?
> 

Thanks for asking this question. I have long been in the scenario you
just described above except that I didn't know of .git/info/exclude all
these days. I was longing to find if there was a way to ignore files in
 a repo without touching the .gitignore of that repo . Now I have found
one, the ".git/info/exclude".

Thanks, again.

-- 
Kaartic

  parent reply	other threads:[~2017-10-06 14:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-06 10:14 is there a truly compelling rationale for .git/info/exclude? rpjday
2017-10-06 12:13 ` Junio C Hamano
2017-10-06 17:39   ` Robert P. J. Day
2017-10-06 19:23     ` Jonathan Nieder
2017-10-07 21:20     ` brian m. carlson
2017-10-12 23:18     ` Johannes Schindelin
2017-10-12 23:56       ` Jeff King
2017-10-13  7:05         ` Robert P. J. Day
2017-10-06 14:18 ` Kaartic Sivaraam [this message]
2017-10-08  8:41 ` Steinar Bang

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=1507299524.12554.9.camel@gmail.com \
    --to=kaartic.sivaraam@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=rpjday@crashcourse.ca \
    /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).