From: Junio C Hamano <gitster@pobox.com>
To: Duy Nguyen <pclouds@gmail.com>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Git Mailing List" <git@vger.kernel.org>,
"Per Lundberg" <per.lundberg@hibox.tv>,
"Steffen Jost" <jost@tcs.ifi.lmu.de>,
"Joshua Jensen" <jjensen@workspacewhiz.com>,
"Matthieu Moy" <git@matthieu-moy.fr>,
"Clemens Buchacher" <drizzd@gmx.net>,
"Holger Hellmuth" <hellmuth@ira.uka.de>,
"Kevin Ballard" <kevin@sb.org>
Subject: Re: [PATCH 1/1] Introduce "precious" file concept
Date: Fri, 22 Feb 2019 10:07:43 -0800 [thread overview]
Message-ID: <xmqqk1hrr91s.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <CACsJy8CB=P9T0XJMWQetExgwDyFN78nuJZq8FtmzG+V1fBY4ig@mail.gmail.com> (Duy Nguyen's message of "Fri, 22 Feb 2019 16:35:44 +0700")
Duy Nguyen <pclouds@gmail.com> writes:
> On Thu, Feb 21, 2019 at 5:39 AM Junio C Hamano <gitster@pobox.com> wrote:
>> > So now you would need to
>> > add more or less the same set of ignore rules in .gitattributes to
>> > mark them trashable, and gitignore/gitattributes rules are not exactly
>> > compatible, you can't just blindly copy them over. Every time you add
>> > one more .gitignore rule, there's a good chance you need to add a
>> > similar rule for trashable attribute.
>>
>> I am not sure why you would even need to _duplicate_.
>>
>> Are you saying for each and every rule that specify "ignored and
>> expendable" in .gitignore there always will be "ignored but
>> precious" exception that match the pattern? Given that we have been
>> OK for so long without even needing "precious", I find it somewhat
>> unrealistic to assume so.
>
> If all ignored files are now redefined as precious and we mark them
> expendable with trashable attribute, then we need to duplicate most of
> the rules. The "precious" attribute of course does not have this
> problem since precious-and-ignored files should be rare.
Ah, so you are saying that ignored (the traditional one we always
had) plus precious is a better combination than ignored (repurposed
to mean ignored-but-precious) plus trashable, because the latter
will cause people configure with a lot of duplication?
If that is the case, I'd agree ;-)
prev parent reply other threads:[~2019-02-22 18:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-16 11:49 [PATCH 0/1] Introduce "precious" file attribute Nguyễn Thái Ngọc Duy
2019-02-16 11:49 ` [PATCH 1/1] Introduce "precious" file concept Nguyễn Thái Ngọc Duy
2019-02-16 19:36 ` Ævar Arnfjörð Bjarmason
2019-02-17 9:31 ` Duy Nguyen
2019-02-18 9:53 ` Ævar Arnfjörð Bjarmason
2019-02-18 10:14 ` Duy Nguyen
2019-02-19 18:08 ` Junio C Hamano
2019-02-20 1:35 ` Duy Nguyen
2019-02-20 8:31 ` Clemens Buchacher
2019-02-20 22:32 ` Junio C Hamano
2019-02-20 9:19 ` Ævar Arnfjörð Bjarmason
2019-02-20 9:36 ` Steffen Jost
2019-02-20 9:41 ` Duy Nguyen
2019-02-20 10:46 ` Ævar Arnfjörð Bjarmason
2019-02-20 11:11 ` Clemens Buchacher
2019-02-22 9:46 ` Duy Nguyen
2019-02-20 22:39 ` Junio C Hamano
2019-02-22 9:35 ` Duy Nguyen
2019-02-22 18:07 ` Junio C Hamano [this message]
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=xmqqk1hrr91s.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=avarab@gmail.com \
--cc=drizzd@gmx.net \
--cc=git@matthieu-moy.fr \
--cc=git@vger.kernel.org \
--cc=hellmuth@ira.uka.de \
--cc=jjensen@workspacewhiz.com \
--cc=jost@tcs.ifi.lmu.de \
--cc=kevin@sb.org \
--cc=pclouds@gmail.com \
--cc=per.lundberg@hibox.tv \
/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).