From: Kenneth Lorber <firstname.lastname@example.org> To: Junio C Hamano <email@example.com> Cc: firstname.lastname@example.org, Kenneth Lorber <email@example.com> Subject: Re: [RFC PATCH v2 3/6] doc: Add namespace collision guidelines file Date: Mon, 1 Jun 2020 19:55:20 -0400 Message-ID: <4654CD5E-6802-4277-AFDE-0DD09A40986B@his.com> (raw) In-Reply-To: <firstname.lastname@example.org> > On May 28, 2020, at 3:29 PM, Junio C Hamano <email@example.com> wrote: > > Junio C Hamano <firstname.lastname@example.org> writes: > >> Kenneth Lorber <email@example.com> writes: >> >>> +Git uses identifiers in a number of different namespaces: >>> + >>> +* environment variables >>> +* files in $GIT_DIR >>> +* files in the working trees >>> +* config sections >>> +* hooks >>> +* attributes >> >> The names of the subcommands "git" can spawn is a shared resource. >> You can install "git-imerge" program in one of the directories on >> your $PATH and say "git imerge" to invoke the program. >> >> Two third-party developers may have to coordinate to avoid giving >> the same name to their totally-unrelated tools, if they hope that >> both of their tools to be useful in the larger Git ecosystem. > > Also names of worktrees that are attached to a single repository. > If a third-party tool wants to make it "easy" for its users by > automatically taking a name to do its job (instead of forcing the > users to come up with a name and giving it to the tool), the name > must be chosen in such a way that it does not collide names in use > and names the user (or other third-party tools) will pick in the > future. One more, but only as an issue to be documented - you don't need to convince me that trying to handle this should simply be declared "left as an exercise for the reader" and that's extensions that require being compiled in to git (so file names, global variables, functions, test names, etc). I'd propose "Do something similar to the above or ask for help on the list" if that's acceptable (where "above" is whatever the current proposal turns into). > > I (or others) may come up with other things that must be named and > name collisions must be avoided. Even though I already said that I > didn't think the "suggestions to avoid name collisions" given by the > RFC PATCH are well done, I do think it is worth being aware of the > problem space, and enumerating what kind of names are shared and > limited resource is the first step to become so. Each message seems less enthusiastic than the last. I'm not sure I see any point in creating a v3 until I have time and inspiration to write something significantly different. > > Thanks. You're welcome. PS - nothing to reply to in the next 2 messages from you. Saved them for v3.
next prev parent reply index Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-17 2:13 [RFC PATCH 0/6] various documentation bits Kenneth Lorber 2020-05-17 2:13 ` [RFC PATCH 1/6] Tell the glossary about core.hooksPath Kenneth Lorber 2020-05-17 18:33 ` Junio C Hamano 2020-05-18 22:06 ` Kenneth Lorber 2020-05-17 2:13 ` [RFC PATCH 2/6] Add bit on extending git to Hacking Git Kenneth Lorber 2020-05-17 18:34 ` Junio C Hamano 2020-05-18 22:10 ` Kenneth Lorber 2020-05-17 2:13 ` [RFC PATCH 3/6] Add namespace collision avoidance guidelines file Kenneth Lorber 2020-05-17 9:45 ` Abhishek Kumar 2020-05-18 15:51 ` Kenneth Lorber 2020-05-17 15:31 ` Junio C Hamano 2020-05-18 21:46 ` Kenneth Lorber 2020-05-17 2:13 ` [RFC PATCH 4/6] Include NAMESPACE COLLISIONS doc into gitrepository-layout.txt Kenneth Lorber 2020-05-18 0:26 ` Junio C Hamano 2020-05-18 23:54 ` Kenneth Lorber 2020-05-17 2:13 ` [RFC PATCH 5/6] Tell config.txt about NAMESPACE COLLISIONS Kenneth Lorber 2020-05-18 0:32 ` Junio C Hamano 2020-05-17 2:13 ` [RFC PATCH 6/6] Add NAMESPACE COLLISIONS reference to Hacking Git Kenneth Lorber 2020-05-17 7:42 ` [RFC PATCH 0/6] various documentation bits Abhishek Kumar 2020-05-17 18:39 ` Junio C Hamano 2020-05-18 23:44 ` Kenneth Lorber 2020-05-18 15:45 ` Kenneth Lorber 2020-05-25 23:27 ` [RFC PATCH v2 " Kenneth Lorber 2020-05-25 23:27 ` [RFC PATCH v2 1/6] doc: Tell the glossary about core.hooksPath Kenneth Lorber 2020-05-26 18:59 ` Junio C Hamano 2020-05-27 16:52 ` Kenneth Lorber 2020-05-27 17:18 ` Kenneth Lorber 2020-05-27 17:18 ` Junio C Hamano 2020-05-25 23:27 ` [RFC PATCH v2 2/6] doc: Add bit on extending git to Hacking Git Kenneth Lorber 2020-05-25 23:27 ` [RFC PATCH v2 3/6] doc: Add namespace collision guidelines file Kenneth Lorber 2020-05-28 18:49 ` Junio C Hamano 2020-05-28 19:29 ` Junio C Hamano 2020-05-29 1:20 ` Junio C Hamano 2020-05-29 18:08 ` Junio C Hamano 2020-06-01 23:55 ` Kenneth Lorber [this message] 2020-06-01 18:38 ` Kenneth Lorber 2020-05-25 23:27 ` [RFC PATCH v2 4/6] doc: Add collision doc to gitrepository-layout.txt Kenneth Lorber 2020-05-25 23:27 ` [RFC PATCH v2 5/6] doc: Tell config.txt about namespace collisions Kenneth Lorber 2020-05-25 23:27 ` [RFC PATCH v2 6/6] doc: Add collision reference to Hacking Git Kenneth Lorber 2020-05-31 21:37 ` [RFC PATCH 0/2] update glossary hooks entry Kenneth Lorber 2020-05-31 21:37 ` [RFC PATCH 1/2] doc: Tell the glossary about core.hooksPath Kenneth Lorber 2020-05-31 21:37 ` [RFC PATCH 2/2] doc: remove dated info and refs to sample hooks Kenneth Lorber
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=4654CD5E-6802-4277-AFDE-0DD09A40986B@his.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ /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
Git Mailing List Archive on lore.kernel.org Archives are clonable: git clone --mirror https://lore.kernel.org/git/0 git/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 git git/ https://lore.kernel.org/git \ email@example.com public-inbox-index git Example config snippet for mirrors Newsgroup available over NNTP: nntp://nntp.lore.kernel.org/org.kernel.vger.git AGPL code for this site: git clone https://public-inbox.org/public-inbox.git