git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: What's cooking in git.git (Apr 2019, #01; Thu, 4)

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 8, 2019, 04:14 UTC
Message-ID
<xmqqimvpb0bd.fsf@gitster-ct.c.googlers.com>
In-Reply-To
<87d0lyanen.fsf@evledraar.gmail.com>
Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
Show 16 quoted lines
>> I'd rather pick between (1) using the final name for the concept we
>> want to eventually achieve, i.e. "precious", and starting small,
>> i.e. "initially, only git-clean knows about it", or (2) doing
>> nothing.  Per-command 'precious-this', 'precious-that' that would be
>> left as interface wart for years is not a pretty sight I want to
>> see.
>
> I think we shouldn't squat "precious" in general without seeing where we
> want to go with it, which I tried to sum up in
> https://public-inbox.org/git/87ftsi68ke.fsf@evledraar.gmail.com/
>
> But aside from that larger discussion, I see no problem with having some
> "+clean" or "-clean" attribute with basically Duy's current patch in
> nd/precious with the equivalent of "s/precious/clean/". Duy suggested
> this in
> https://public-inbox.org/git/CACsJy8C377NmLv9edNYjinKAQf-P1y5+Nwhdj3vRkz_E__x43Q@mail.gmail.com/

I know. I've already said that we do not want proliferation of precious-clean precious-merge precious-yet-another-thing.

> ... shouldn't be breaking the reasonable assumption a user of "-x"
> could make so far, which is "ignore repo config, just wipe it
> all".

Yup. I think that is reasonable. To paraphrase (so that you can tell me that I misunderstood you, if that is the case), if we are told to honor only what the index knows, deliberately ignoring the .gitignore file, then we should also ignore .gitattributes that says which ones are ignored-but-precious, as the "precious" attribute is a mere implementation detail of what _could_ have been part of the exclude mechanism (aka ".gitignore") from day one, if we designed the exclude mechanism to support "ignored and expendable" and "ignored and precious" from day one. "clean -x" would certainly have ignored both kinds.

Previous: Ævar Arnfjörð BjarmasonNext: Nguyễn Thái Ngọc Duy
Message 5 of 19 in “What's cooking in git.git (Apr 2019, #01; Thu, 4)”
  1. Junio C HamanoApr 4, 2019
  2. Duy NguyenApr 4, 2019
  3. Junio C HamanoApr 4, 2019
  4. Ævar Arnfjörð BjarmasonApr 6, 2019
  5. Junio C HamanoApr 8, 2019
  6. Introduce "precious" file conceptNguyễn Thái Ngọc Duy, Apr 9, 2019
  7. Junio C HamanoApr 9, 2019
  8. Duy NguyenApr 10, 2019
  9. Junio C HamanoApr 12, 2019
  10. Eric SunshineApr 9, 2019
  11. Ævar Arnfjörð BjarmasonApr 12, 2019
  12. Duy NguyenApr 13, 2019
  13. Todd ZullingerApr 5, 2019
  14. Junio C HamanoApr 5, 2019
  15. Ævar Arnfjörð BjarmasonApr 6, 2019
  16. Junio C HamanoApr 8, 2019
  17. Ævar Arnfjörð BjarmasonApr 6, 2019
  18. Junio C HamanoApr 8, 2019
  19. Josh SteadmonApr 8, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.