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

Re: [Outreachy] [PATCH v2] diff: do not show submodule with untracked files as "-dirty"

From
Eric Sunshine <sunshine@sunshineco.com>
Date
Oct 21, 2020, 23:04 UTC
Message-ID
<CAPig+cRLGsSzHZ-280WJD1vMLvK-kL2EEg3mc8gFiEEa8Tj6Aw@mail.gmail.com>
In-Reply-To
<CAHjREB6Agm9Nia2+e4=1zAJ6Y3NXgPQLmN_he1353ScaznK5hQ@mail.gmail.com>
On Wed, Oct 21, 2020 at 3:40 PM Sangeeta NB <sangunb09@gmail.com> wrote:
Show 12 quoted lines
> > Another option is to have a preparatory patch which first modernizes
> > the script, and then your new tests would follow modern style. But,
> > that may be outside of scope of your submission.
> >
> > To summarize: The only really actionable review comments are the minor
> > style nits in the C code. The nits about style issues in the tests are
> > judgement calls, and could be handled (by someone) at a later date.
>
> For the style issues in the tests maybe what I can do is I can submit
> another patch with this patch to modernize the test scripts of these
> files? I am expecting some feedback from the community on how to
> handle this.

If this is a microproject, then it probably makes sense just to fix the remaining style nits in the C code, and leave it at that.

Even if this is not a microproject, the answer really depends upon how much time and effort you want to devote to this. As a reviewer, I don't demand or expect you to fix all the problems in the old test scripts just to get the change accepted which prompted your submission in the first place. It's important to focus on that first rather than getting sidetracked working on stuff which may not be important to your primary goal. Also, keep in mind that fixing all the style issues in those old test scripts may require multiple preparatory patches, rather than just one, and multiple re-rolls, which could end up eating up a lot of extra time to get it all polished properly.

For these reasons, I'm inclined to suggest polishing the current submission to get it accepted. Then decide afterward if you want to devote time to working on these ancillary tasks.

Previous: Sangeeta NBNext: Sangeeta Jain
Message 8 of 36 in “diff: do not show submodule with untracked files as "-dirty"”
  1. diff: do not show submodule with untracked files as "-dirty"Sangeeta via GitGitGadget, Oct 15, 2020
  2. Phillip WoodOct 20, 2020
  3. Sangeeta NBOct 20, 2020
  4. Phillip WoodOct 21, 2020
  5. [Outreachy] [PATCH v2] diff: do not show submodule with untracked files as "-dirty"Sangeeta Jain, Oct 21, 2020
  6. Eric SunshineOct 21, 2020
  7. Sangeeta NBOct 21, 2020
  8. Eric SunshineOct 21, 2020
  9. [Outreachy] [PATCH v3] diff: do not show submodule with untracked files as "-dirty"Sangeeta Jain, Oct 22, 2020
  10. Junio C HamanoOct 22, 2020
  11. Sangeeta NBOct 23, 2020
  12. Junio C HamanoOct 23, 2020
  13. Sangeeta NBOct 23, 2020
  14. Junio C HamanoOct 23, 2020
  15. Sangeeta NBOct 23, 2020
  16. diff: do not show submodule with untracked files as "-dirty"Sangeeta Jain, Oct 23, 2020
  17. Junio C HamanoOct 23, 2020
  18. Sangeeta NBOct 23, 2020
  19. Junio C HamanoOct 23, 2020
  20. [Outreachy] [PATCH v4] diff: do not show submodule with untracked files as "-dirty"Sangeeta Jain, Oct 23, 2020
  21. Junio C HamanoOct 23, 2020
  22. Sangeeta NBOct 25, 2020
  23. Junio C HamanoOct 26, 2020
  24. [Outreachy] [PATCH v5] diff: do not show submodule with untracked files as "-dirty"Sangeeta Jain, Oct 23, 2020
  25. [Outreachy][PATCH v6] diff: do not show submodule with untracked files as "-dirty"Sangeeta Jain, Oct 26, 2020
  26. SangeetaNov 3, 2020
  27. Junio C HamanoNov 3, 2020
  28. SangeetaNov 7, 2020
  29. Junio C HamanoDec 8, 2020
  30. Đoàn Trần Công DanhNov 7, 2020
  31. SangeetaNov 9, 2020
  32. Junio C HamanoNov 9, 2020
  33. [Outreachy][PATCH v7] diff: do not show submodule with untracked files as "-dirty"Sangeeta Jain, Nov 10, 2020
  34. Đoàn Trần Công DanhNov 10, 2020
  35. SangeetaDec 8, 2020
  36. Junio C HamanoDec 8, 2020

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.