{"thread":{"id":"64000","subject":"[PATCH gitk] gitk: add README.md with contribution guidelines","startedAt":"2025-08-20T19:53:40Z","lastAt":"2025-08-21T07:15:21Z","messageCount":9,"participants":["Michael Rappazzo","Junio C Hamano","Mike Rappazzo","Kristoffer Haugsbakk","D. Ben Knoble","Johannes Sixt"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"524554","messageId":"20250820195229.45943-1-rappazzo@gmail.com","threadId":"64000","inReplyTo":null,"subject":"[PATCH gitk] gitk: add README.md with contribution guidelines","fromName":"Michael Rappazzo","fromEmail":"rappazzo@gmail.com","sentAt":"2025-08-20T19:52:29Z","receivedAt":"2025-08-20T19:53:40Z","isPatch":true,"sender":{"key":"rappazzo@gmail.com","avatar":"https://avatars.githubusercontent.com/u/525287?v=4"},"body":"Signed-off-by: Michael Rappazzo \n---\n README.md | 63 +++++++++++++++++++++++++++++++++++++++++++++++++++++++\n 1 file changed, 63 insertions(+)\n create mode 100644 README.md\n\ndiff --git a/README.md b/README.md\nnew file mode 100644\nindex 0000000000..adf7a0ba85\n--- /dev/null\n+++ b/README.md\n@@ -0,0 +1,63 @@\n+# gitk - The Git Repository Browser\n+\n+This is the official repository for gitk, a graphical Git repository browser.\n+\n+## Repository Status\n+\n+- **Official Repository**: https://github.com/j6t/gitk\n+- **Integration**: This repository is regularly merged into the main Git repository (git.git) via subtree merges into the `gitk-git/` subdirectory\n+\n+## Contributing\n+\n+Contributions are welcome! The preferred method for submitting patches is via email to the Git mailing list, as this allows for more thorough review and broader community feedback. However, GitHub pull requests are also accepted.\n+\n+All commits must be signed off (use `git commit --signoff`).\n+\n+### Email Patches\n+- Create patches from this repository (github.com/j6t/gitk), not from the `gitk-git/` subdirectory in git.git\n+- Send patches to the Git mailing list: git@vger.kernel.org and CC the maintainer: j6t@kdbg.org\n+- Follow the Git project's patch submission guidelines\n+- Include `[PATCH gitk]` in the subject line\n+\n+#### Creating and Sending Patches\n+After committing your changes:\n+```bash\n+git format-patch -1 --subject-prefix=\"PATCH gitk\"\n+git send-email --to=git@vger.kernel.org --cc=j6t@kdbg.org *.patch\n+```\n+\n+For `git send-email` configuration, see the [documentation](https://git-scm.com/docs/git-send-email) (search for \"Examples of SMTP Servers\").\n+\n+For information about subscribing to the Git mailing list, see [subscription info](https://git.wiki.kernel.org/index.php/GitCommunity). Note that subscription is not required to participate in patch discussions.\n+\n+### GitHub Pull Requests\n+- Fork this repository and create a feature branch\n+- Submit a pull request with a clear description of your changes\n+\n+## Building\n+\n+gitk is a Tcl/Tk application. It requires Tcl/Tk to be installed on your system.\n+\n+### Running directly\n+```bash\n+./gitk\n+```\n+\n+### Installation\n+To install system-wide, you can use either `make` or `meson`:\n+\n+```bash\n+# Using Make\n+make install\n+\n+# Using Meson\n+meson setup builddir\n+meson compile -C builddir\n+meson install -C builddir\n+```\n+\n+Both build systems will handle setting the correct Tcl/Tk interpreter path and installing translation files.\n+\n+## License\n+\n+gitk is distributed under the GNU General Public License, either version 2, or (at your option) any later version.\n\\ No newline at end of file\n-- \n2.51.0\n\n"},{"id":"524562","messageId":"xmqq349laeyb.fsf@gitster.g","threadId":"64000","inReplyTo":"20250820195229.45943-1-rappazzo@gmail.com","subject":"Re: [PATCH gitk] gitk: add README.md with contribution guidelines","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2025-08-20T20:57:48Z","receivedAt":"2025-08-20T20:57:51Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Michael Rappazzo writes:\n\n> +#### Creating and Sending Patches\n> +After committing your changes:\n> +```bash\n> +git format-patch -1 --subject-prefix=\"PATCH gitk\"\n> +git send-email --to=git@vger.kernel.org --cc=j6t@kdbg.org *.patch\n> +```\n\nJust being curious, but does the project strongly discourage a\nmulti-patch topic?\n\nIt would be really nice if you add \"review them here before you run\nsend-email\" step between these two commands ;-).\n\nThanks.\n"},{"id":"524565","messageId":"CANoM8SVTROfaQpRNBfwxU9opjXFPLzxN1W-xXTrA2bhx9KJ0LQ@mail.gmail.com","threadId":"64000","inReplyTo":"xmqq349laeyb.fsf@gitster.g","subject":"Re: [PATCH gitk] gitk: add README.md with contribution guidelines","fromName":"Mike Rappazzo","fromEmail":"rappazzo@gmail.com","sentAt":"2025-08-20T21:02:47Z","receivedAt":"2025-08-20T21:03:01Z","isPatch":true,"sender":{"key":"rappazzo@gmail.com","avatar":"https://avatars.githubusercontent.com/u/525287?v=4"},"body":"On Wed, Aug 20, 2025 at 4:57 PM Junio C Hamano wrote:\n>\n> Michael Rappazzo writes:\n>\n> > +#### Creating and Sending Patches\n> > +After committing your changes:\n> > +```bash\n> > +git format-patch -1 --subject-prefix=\"PATCH gitk\"\n> > +git send-email --to=git@vger.kernel.org --cc=j6t@kdbg.org *.patch\n> > +```\n>\n> Just being curious, but does the project strongly discourage a\n> multi-patch topic?\n\nI don't believe so. I think most people know how to submit a github\nPR, but J6t has mentioned that he prefers the mailing list (as noted\nin the readme). So I wrote a simple example to show that patching by\nemail doesn't have to be scary.\n\n>\n> It would be really nice if you add \"review them here before you run\n> send-email\" step between these two commands ;-).\n\nI can revise. I will wait for more comments before sending a v2.\n"},{"id":"524567","messageId":"70e08a97-ca6a-4899-b779-1ed436b76fb7@app.fastmail.com","threadId":"64000","inReplyTo":"xmqq349laeyb.fsf@gitster.g","subject":"Re: [PATCH gitk] gitk: add README.md with contribution guidelines","fromName":"Kristoffer Haugsbakk","fromEmail":"kristofferhaugsbakk@fastmail.com","sentAt":"2025-08-20T21:03:45Z","receivedAt":"2025-08-20T21:04:10Z","isPatch":true,"sender":{"key":"kristofferhaugsbakk@fastmail.com","avatar":null},"body":"On Wed, Aug 20, 2025, at 22:57, Junio C Hamano wrote:\n> Michael Rappazzo writes:\n>\n>> +#### Creating and Sending Patches\n>> +After committing your changes:\n>> +```bash\n>> +git format-patch -1 --subject-prefix=\"PATCH gitk\"\n>> +git send-email --to=git@vger.kernel.org --cc=j6t@kdbg.org *.patch\n>> +```\n>\n> Just being curious, but does the project strongly discourage a\n> multi-patch topic?\n>\n> It would be really nice if you add \"review them here before you run\n> send-email\" step between these two commands ;-).\n\nI alwyays use\n\n git format-patch ... -opatchez\n cat patchez/* | less\n\nBecause sending out something weird to a mailing list gives me the\nchills. (And there might be format-patch bugs.)\n\n-- \nKristoffer Haugsbakk\n"},{"id":"524570","messageId":"xmqqldnd8zpc.fsf@gitster.g","threadId":"64000","inReplyTo":"CANoM8SVTROfaQpRNBfwxU9opjXFPLzxN1W-xXTrA2bhx9KJ0LQ@mail.gmail.com","subject":"Re: [PATCH gitk] gitk: add README.md with contribution guidelines","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2025-08-20T21:12:31Z","receivedAt":"2025-08-20T21:12:33Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Mike Rappazzo writes:\n\n> On Wed, Aug 20, 2025 at 4:57 PM Junio C Hamano wrote:\n>>\n>> Michael Rappazzo writes:\n>>\n>> > +#### Creating and Sending Patches\n>> > +After committing your changes:\n>> > +```bash\n>> > +git format-patch -1 --subject-prefix=\"PATCH gitk\"\n>> > +git send-email --to=git@vger.kernel.org --cc=j6t@kdbg.org *.patch\n>> > +```\n>>\n>> Just being curious, but does the project strongly discourage a\n>> multi-patch topic?\n>\n> I don't believe so. I think most people know how to submit a github\n> PR, but J6t has mentioned that he prefers the mailing list (as noted\n> in the readme). So I wrote a simple example to show that patching by\n> email doesn't have to be scary.\n\nAs the original assumes that you are on the branch where you are\ntaking the patch(es) from, perhaps\n\n $ git format-patch --subject-prefix='PATCH gitk' @{u}..\n\nwould work? I was mostly reacting to the \"-1\" on the command line.\n\n>> It would be really nice if you add \"review them here before you run\n>> send-email\" step between these two commands ;-).\n>\n> I can revise. I will wait for more comments before sending a v2.\n\nThanks.\n"},{"id":"524572","messageId":"xmqqfrdl8zjm.fsf@gitster.g","threadId":"64000","inReplyTo":"70e08a97-ca6a-4899-b779-1ed436b76fb7@app.fastmail.com","subject":"Re: [PATCH gitk] gitk: add README.md with contribution guidelines","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2025-08-20T21:15:57Z","receivedAt":"2025-08-20T21:16:00Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"\"Kristoffer Haugsbakk\" writes:\n\n>> It would be really nice if you add \"review them here before you run\n>> send-email\" step between these two commands ;-).\n>\n> I alwyays use\n>\n> git format-patch ... -opatchez\n> cat patchez/* | less\n>\n> Because sending out something weird to a mailing list gives me the\n> chills. (And there might be format-patch bugs.)\n\nThanks for a tip.\n\nIt matches what I do, except that I use ./+jc//\ndirectories as the staging area, as I tend to keep what I sent out\nfor a few days, and I strongly prefer to give its own directory to\neach topic, to avoid \"git send-email *.patch\" sending out random\nunrelated patches.\n"},{"id":"524574","messageId":"CANoM8SX7_uQV-ZRAim55UaiHYCKTgKN0AO6zB1O7Ux4deiCNaw@mail.gmail.com","threadId":"64000","inReplyTo":"xmqqldnd8zpc.fsf@gitster.g","subject":"Re: [PATCH gitk] gitk: add README.md with contribution guidelines","fromName":"Mike Rappazzo","fromEmail":"rappazzo@gmail.com","sentAt":"2025-08-20T21:20:20Z","receivedAt":"2025-08-20T21:20:34Z","isPatch":true,"sender":{"key":"rappazzo@gmail.com","avatar":"https://avatars.githubusercontent.com/u/525287?v=4"},"body":"On Wed, Aug 20, 2025 at 5:12 PM Junio C Hamano wrote:\n>\n> Mike Rappazzo writes:\n>\n> > On Wed, Aug 20, 2025 at 4:57 PM Junio C Hamano wrote:\n> >>\n> >> Michael Rappazzo writes:\n> >>\n> >> > +#### Creating and Sending Patches\n> >> > +After committing your changes:\n> >> > +```bash\n> >> > +git format-patch -1 --subject-prefix=\"PATCH gitk\"\n> >> > +git send-email --to=git@vger.kernel.org --cc=j6t@kdbg.org *.patch\n> >> > +```\n> >>\n> >> Just being curious, but does the project strongly discourage a\n> >> multi-patch topic?\n> >\n> > I don't believe so. I think most people know how to submit a github\n> > PR, but J6t has mentioned that he prefers the mailing list (as noted\n> > in the readme). So I wrote a simple example to show that patching by\n> > email doesn't have to be scary.\n>\n> As the original assumes that you are on the branch where you are\n> taking the patch(es) from, perhaps\n>\n> $ git format-patch --subject-prefix='PATCH gitk' @{u}..\n>\n> would work? I was mostly reacting to the \"-1\" on the command line.\n\n`@{u}..` is funny, because that seems to assume that you haven't\npushed your changes to its upstream yet. I could say `master..` but\nthat assumes that you named the branch that (as opposed to `main` or\nsomething). I will try a few different ways and see how they feel.\nAs I said, I just wanted an example to demystify patching by email. I\nthink if I add something above to clarify that this is just an example\nand not verbose instructions it could help too.\n\n>\n> >> It would be really nice if you add \"review them here before you run\n> >> send-email\" step between these two commands ;-).\n> >\n> > I can revise. I will wait for more comments before sending a v2.\n>\n> Thanks.\n"},{"id":"524588","messageId":"CALnO6CBznUApKLv2pQbX9QJBU=O6R3MTo42AePp0kp2X-x3Vag@mail.gmail.com","threadId":"64000","inReplyTo":"CANoM8SX7_uQV-ZRAim55UaiHYCKTgKN0AO6zB1O7Ux4deiCNaw@mail.gmail.com","subject":"Re: [PATCH gitk] gitk: add README.md with contribution guidelines","fromName":"D. Ben Knoble","fromEmail":"ben.knoble@gmail.com","sentAt":"2025-08-20T23:42:16Z","receivedAt":"2025-08-20T23:42:29Z","isPatch":true,"sender":{"key":"ben.knoble@gmail.com","avatar":"https://avatars.githubusercontent.com/u/22802209?v=4"},"body":"On Wed, Aug 20, 2025 at 5:20 PM Mike Rappazzo wrote:\n>\n> On Wed, Aug 20, 2025 at 5:12 PM Junio C Hamano wrote:\n> >\n> > Mike Rappazzo writes:\n> >\n> > > On Wed, Aug 20, 2025 at 4:57 PM Junio C Hamano wrote:\n> > >>\n> > >> Michael Rappazzo writes:\n> > >>\n> > >> > +#### Creating and Sending Patches\n> > >> > +After committing your changes:\n> > >> > +```bash\n> > >> > +git format-patch -1 --subject-prefix=\"PATCH gitk\"\n> > >> > +git send-email --to=git@vger.kernel.org --cc=j6t@kdbg.org *.patch\n> > >> > +```\n> > >>\n> > >> Just being curious, but does the project strongly discourage a\n> > >> multi-patch topic?\n> > >\n> > > I don't believe so. I think most people know how to submit a github\n> > > PR, but J6t has mentioned that he prefers the mailing list (as noted\n> > > in the readme). So I wrote a simple example to show that patching by\n> > > email doesn't have to be scary.\n> >\n> > As the original assumes that you are on the branch where you are\n> > taking the patch(es) from, perhaps\n> >\n> > $ git format-patch --subject-prefix='PATCH gitk' @{u}..\n> >\n> > would work? I was mostly reacting to the \"-1\" on the command line.\n>\n> `@{u}..` is funny, because that seems to assume that you haven't\n> pushed your changes to its upstream yet. I could say `master..` but\n> that assumes that you named the branch that (as opposed to `main` or\n> something). I will try a few different ways and see how they feel.\n> As I said, I just wanted an example to demystify patching by email. I\n> think if I add something above to clarify that this is just an example\n> and not verbose instructions it could help too.\n\nIt is less funny when @{u} is the branch you started your work from\nand where you hope to integrate to, as in\n\n git switch -c topic origin/master\n\nor something.\n\nThen, you might use @{push} to refer to that \"somewhere else\" you push\nto that is not the place to which you hope your changes will go. It is\ncertainly different from lots of GitHub- and similar tutorials that\nencourage \"git push -u ,\" which sets @{upstream} to\nwhat I prefer to use @{push} for. Granted, those tutorials use\nsomething closer to a centralized workflow, and what I'm describing\n(what mailing list flows are?) is more triangular.\n\n> > >> It would be really nice if you add \"review them here before you run\n> > >> send-email\" step between these two commands ;-).\n> > >\n> > > I can revise. I will wait for more comments before sending a v2.\n\nLinking to https://git-send-email.io/ is probably the best advice on\nmaking sending patches less scary.\n\n-- \nD. Ben Knoble\n"},{"id":"524604","messageId":"0e7cacac-b113-49de-be4b-a689e81815fb@kdbg.org","threadId":"64000","inReplyTo":"20250820195229.45943-1-rappazzo@gmail.com","subject":"Re: [PATCH gitk] gitk: add README.md with contribution guidelines","fromName":"Johannes Sixt","fromEmail":"j6t@kdbg.org","sentAt":"2025-08-21T07:15:03Z","receivedAt":"2025-08-21T07:15:21Z","isPatch":true,"sender":{"key":"j6t@kdbg.org","avatar":"https://avatars.githubusercontent.com/u/14810926?v=4"},"body":"Thank you. However, I hate to say that this isn't the text that I would\nexpect on the front page of the repository.\n\nAn important part is missing: first-time visitors are not addressed at\nall. We should state what this software is about and show examples how\nto use it effectively, perhaps include a link to the manual\n(https://git-scm.com/docs/gitk).\n\nI would prefer not to have format-patch+send-email tutorial in this text\nnor how to make Github PRs. It is OK to have links to tutorials. The\nprefix [PATCH gitk] hasn't been used in the past, but we do have the\nconvention that commit summaries have the prefix 'gitk:'. This alone\ndistinguishes submissions sufficiently (and then also simplifies using\n'git format-patch' a bit).\n\nDo not say that \"this is the official repository\". Remember that every\nclone would say that, too. That would be confusing. In the Git world,\nthis status isn't achieved by proclamation, but by convention.\n\nI wouldn't include the details how Gitk is also shipped with the Git\nrepository, but at most that it is. It is not even necessary to\ndiscourage people from making patches in the gitk-git/ directory. `git\nam -3` can cope with such patches quite well. Allowing such\ncontributions lowers the entry barrier.\n\n\nAm 20.08.25 um 21:52 schrieb Michael Rappazzo:\n> Signed-off-by: Michael Rappazzo \n> ---\n> README.md | 63 +++++++++++++++++++++++++++++++++++++++++++++++++++++++\n> 1 file changed, 63 insertions(+)\n> create mode 100644 README.md\n> \n> diff --git a/README.md b/README.md\n> new file mode 100644\n> index 0000000000..adf7a0ba85\n> --- /dev/null\n> +++ b/README.md\n> @@ -0,0 +1,63 @@\n> +# gitk - The Git Repository Browser\n> +\n> +This is the official repository for gitk, a graphical Git repository browser.\n> +\n> +## Repository Status\n> +\n> +- **Official Repository**: https://github.com/j6t/gitk\n> +- **Integration**: This repository is regularly merged into the main Git repository (git.git) via subtree merges into the `gitk-git/` subdirectory\n> +\n> +## Contributing\n> +\n> +Contributions are welcome! The preferred method for submitting patches is via email to the Git mailing list, as this allows for more thorough review and broader community feedback. However, GitHub pull requests are also accepted.\n> +\n> +All commits must be signed off (use `git commit --signoff`).\n> +\n> +### Email Patches\n> +- Create patches from this repository (github.com/j6t/gitk), not from the `gitk-git/` subdirectory in git.git\n> +- Send patches to the Git mailing list: git@vger.kernel.org and CC the maintainer: j6t@kdbg.org\n> +- Follow the Git project's patch submission guidelines\n> +- Include `[PATCH gitk]` in the subject line\n> +\n> +#### Creating and Sending Patches\n> +After committing your changes:\n> +```bash\n> +git format-patch -1 --subject-prefix=\"PATCH gitk\"\n> +git send-email --to=git@vger.kernel.org --cc=j6t@kdbg.org *.patch\n> +```\n> +\n> +For `git send-email` configuration, see the [documentation](https://git-scm.com/docs/git-send-email) (search for \"Examples of SMTP Servers\").\n> +\n> +For information about subscribing to the Git mailing list, see [subscription info](https://git.wiki.kernel.org/index.php/GitCommunity). Note that subscription is not required to participate in patch discussions.\n> +\n> +### GitHub Pull Requests\n> +- Fork this repository and create a feature branch\n> +- Submit a pull request with a clear description of your changes\n> +\n> +## Building\n> +\n> +gitk is a Tcl/Tk application. It requires Tcl/Tk to be installed on your system.\n> +\n> +### Running directly\n> +```bash\n> +./gitk\n> +```\n> +\n> +### Installation\n> +To install system-wide, you can use either `make` or `meson`:\n> +\n> +```bash\n> +# Using Make\n> +make install\n> +\n> +# Using Meson\n> +meson setup builddir\n> +meson compile -C builddir\n> +meson install -C builddir\n> +```\n> +\n> +Both build systems will handle setting the correct Tcl/Tk interpreter path and installing translation files.\n> +\n> +## License\n> +\n> +gitk is distributed under the GNU General Public License, either version 2, or (at your option) any later version.\n> \\ No newline at end of file\n\n"}]}