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

Re: [PATCH v2 2/2] Provide better guidance for submitting patches against upstream utilities

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 31, 2012, 23:39 UTC
Message-ID
<7vzk0tdc63.fsf@alter.siamese.dyndns.org>
In-Reply-To
<1356992375-11116-3-git-send-email-jason.k.holden.swdev@gmail.com>
Jason Holden <jason.k.holden.swdev@gmail.com> writes:
Show 20 quoted lines
> git-gui, gitk, and git-po are maintained upstream of git.
> Document this, and the procedure for submitting patches to these tools
>
> Signed-off-by: Jason Holden <jason.k.holden.swdev@gmail.com>
> ---
>  Documentation/SubmittingPatches | 11 +++++++++++
>  1 file changed, 11 insertions(+)
>
> diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
> index 75935d5..30b95a8 100644
> --- a/Documentation/SubmittingPatches
> +++ b/Documentation/SubmittingPatches
> @@ -58,6 +58,17 @@ Checklist (and a short version for the impatient):
>  	  please test it first by sending email to yourself.
>  	- see below for instructions specific to your mailer
>  
> +	Improving upstream utilities (gitk, git-gui, git-po)
> +	- gitk, git-gui, and git-po are maintained upstream of Git
> +	  despite being included in Git's git repository
> +	- Patches should be made against the upstream gui repository,
GUI?
Show 5 quoted lines
> +	  and not against the version in Git's git repository
> +	- The resulting patch should still be emailed for review
> +	  to the git mailing list (git@vger.kernel.org), cc'ing the
> +	  applicable gui maintainer
> +	- Please see the MAINTAINER's file for the gui maintainer's contact
GUI?
Perhaps "parts with sub-maintainers' with their own repositories".

In any case, I think it is probably much better not to add a new file at the top of the tree only to hold twenty-or-so lines. Instead, add the contents as a footnote to this file and refer to it from here.

Previous: Jason Holden
Message 5 of 5 in “Add MAINTAINERS file and clarify gui workflows”
  1. 0/2 Add MAINTAINERS file and clarify gui workflowsJason Holden, Dec 31, 2012
  2. 1/2 Add top-level maintainers file with email/canonical repository informationJason Holden, Dec 31, 2012
  3. Jacob HelwigDec 31, 2012
  4. 2/2 Provide better guidance for submitting patches against upstream utilitiesJason Holden, Dec 31, 2012
  5. Junio C HamanoDec 31, 2012

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.