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

Re: [GSoC][PATCH] microporject test_path_is_*

From
Elijah Newren <newren@gmail.com>
Date
Mar 28, 2019, 16:02 UTC
Message-ID
<CABPp-BGiP8BZwWQMbYhVQjqq8jZx+bbUTfgLaC6ZyukpLErZBw@mail.gmail.com>
In-Reply-To
<BF34A383-7714-40CC-B5EF-4FD20E7AC839@m-mooga.com>
On Wed, Mar 27, 2019 at 1:31 PM Mooga <contact@m-mooga.com> wrote:
Show 6 quoted lines
>
> Hi Eliah,
> thanks for the advice, but still after I read the  SubmittingPatches , and see around the Submitting patches process still confussing for me , there's a better way  for explanation as an example
>
>
> Regards

On this list, please respond to emails interleaved or below the original email; we discourage top-posting.

What part of the process is confusing? Without knowing that, we're likely to just repeat the document as it stands. Also, have you taken a look at https://gitgitgadget.github.io/ (which is a new thing designed to make submitting patches to git.git easier)?

Hope that helps, Elijah

Previous: MoogaNext: Mooga
Message 4 of 6 in “microporject test_path_is_*”
  1. MoogaMar 27, 2019
  2. Elijah NewrenMar 27, 2019
  3. MoogaMar 27, 2019
  4. Elijah NewrenMar 28, 2019
  5. MoogaMar 28, 2019
  6. Elijah NewrenMar 28, 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.