From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>
Subject: Re: is there a truly compelling rationale for .git/info/exclude?
Date: Fri, 13 Oct 2017 01:18:00 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1.1710130116430.40514@virtualbox> (raw)
In-Reply-To: <alpine.LFD.2.21.1710061337300.14079@localhost.localdomain>
Hi Robert,
[who I had to cull from the To:/Cc: headers, as my mailer consistently
told me that there is no valid DNS record to route mail to
rpjday@crashcourse.ca, which *is* weird.]
On Fri, 6 Oct 2017, Robert P. J. Day wrote:
> On Fri, 6 Oct 2017, Junio C Hamano wrote:
>
> > Don't waste time by seeking a "compelling" reason. A mere "this is
> > the most expedite way to gain convenience" back when something was
> > introduced could be an answer, and it is way too late to complain
> > about such a choice anyway.
>
> perfectly respectable answer ... it tells me that, between .gitignore
> files and core.excludesFile, there's not much left for
> .git/info/exclude to do, except in weird circumstances.
I use .git/info/exclude to keep worktrees in subdirectories of the "main"
worktree.
That's not really weird. It's just something few people do, but that's not
the same as "weird".
Ciao,
Johannes
next prev parent reply other threads:[~2017-10-12 23:18 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 [this message]
2017-10-12 23:56 ` Jeff King
2017-10-13 7:05 ` Robert P. J. Day
2017-10-06 14:18 ` Kaartic Sivaraam
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.21.1.1710130116430.40514@virtualbox \
--to=johannes.schindelin@gmx.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.