Hi Randall, On 2015-06-21 07:09, Randall S. Becker wrote: > On June 21, 2015 12:56 AM, Michael Haggerty wrote: > >> As for thinking of a shorter name for the option: assuming the blob integrity >> checks can be turned on and off independently as described above, then I >> think >> it is reasonable to *also* add a `--quick` option defined as >> >> --quick: Skip some expensive checks, dramatically reducing the >> runtime of `git fsck`. Currently this is equivalent to >> `--no-check-blob-integrity`. >> >> In the future if we invent other expensive checks we might also add them to >> the >> list of things that are skipped by `--quick`. > > Synonym suggestions: --links or --relations > I was going to include --refs but that may be ambiguous. Links also has > meaning so it's probably out and --hitch may just be silly and needlessly > introducing a new term.
I appreciate your input, but I think in this case, "links" and "relations" would just add new terminology, and I would like to keep using existing terminology as much as possible (because we already have a confusingly large glossary). I also see "link" as a problematic term because it resembles "gitlink" -- which means something entirely different. My favorite is still `--quick` because in contrast to Junio, to me it *has* a connotation of "less thoroughly". "Get rich quick" just does not mean "Earn a lot of money by doing a thorough job, just faster than you usually would". If Junio insists, I will of course rename it to `--skip-blobs` because that is really what we do. However, it has been my experience over and over again that letting implementation details bleed through to the user interface always comes back to haunt you[*1*]. In this case, the purpose of the option really just was to cut a few corners to run `git fsck` more quickly. The fact that the corner I cut here is to skip unpacking of the blobs just happens to be the implementation detail. So, Junio, what is it: keep `--quick` and clarify in the documentation that we cut corners (and which corners), or rename it to `--skip-blobs`? Your call. Ciao, Dscho Footnote *1*: You would not believe how often I had to apologize for renaming the `edit-patch-series` script to `interactive rebase`. You see, technically it is correct to call it an interactive rebase: it really is that, from a purely technical, soul-less point of view. From the users' point of view, however, the name `edit-patch-series` would relate exactly what the command is *about*, as opposed to *how* it works. To most users, calling it "rebase -i" is as understandable as "sympodial fasciculation and regrafting of disconnate vernates" (and don't ask me what that even means). -- To unsubscribe from this list: send the line "unsubscribe git" in
