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

Re: [PATCH 2/2] doc: add another way to identify if a patch has been merged

From
Kaartic Sivaraam <kaarticsivaraam91196@gmail.com>
Date
Aug 2, 2017, 12:32 UTC
Message-ID
<1501677122.1957.8.camel@gmail.com>
In-Reply-To
<CAGZ79kZgV1=2HcYeXyoCy2Jk6v__trvTh_-rH+kbFX7fgWziyw@mail.gmail.com>
On Tue, 2017-08-01 at 10:46 -0700, Stefan Beller wrote:
Show 16 quoted lines
> Actually I am slightly negative on this one, because of
> occurrences like [1].
> 
> Our SubmittingPatches is already considered *too long* for most people
> who just want to drop a drive-by patch.
> 
> Adding more knowledge (which btw is about general git usage and not
> specific to our development workflow; you'd find the same tip in the
> kernel community).
> 
> I wonder if we need a document that describes workflows.
> (Oh, look we have 'man gitworkflows'! I did not know)
> 
> So maybe we want to cut a lot of workflow related commendatory from
> the SubmitingPatches and then encourage to read such man page?
>

That's right. Maybe Documentation/SubmittingPatches needs a revamp to be one-time contributor friendly? Maybe introducing a "gist" for people who do not have the time to read the whole document, might be of help?

Show 7 quoted lines
> [1 ]https://public-inbox.org/git/CA+dzEB=cDvp7ZS8x+p+U-5NbK3SNd0FPyj_wP=gvi8mJi6D2ag@mail.gmail.com/
> 
> 
> 
> > --
> > 2.14.0.rc1.434.g6eded367a
> > 
-- 
Kaartic
Previous: Stefan BellerNext: Junio C Hamano
Message 17 of 23 in “doc: fix small issues in SubmittingPatches”
  1. 1/2 doc: fix small issues in SubmittingPatchesKaartic Sivaraam, Jul 30, 2017
  2. 2/2 doc: add another way to identify if a patch has been mergedKaartic Sivaraam, Jul 30, 2017
  3. Philip OakleyJul 30, 2017
  4. Kaartic SivaraamJul 30, 2017
  5. 1/2 doc: fix small issues in SubmittingPatchesKaartic Sivaraam, Jul 30, 2017
  6. Stefan BellerJul 31, 2017
  7. Junio C HamanoJul 31, 2017
  8. Kaartic SivaraamAug 1, 2017
  9. Stefan BellerAug 1, 2017
  10. Kaartic SivaraamAug 2, 2017
  11. Junio C HamanoAug 2, 2017
  12. Stefan BellerAug 2, 2017
  13. Kaartic SivaraamAug 3, 2017
  14. 1/2 doc: fix small issues in SubmittingPatchesKaartic Sivaraam, Aug 1, 2017
  15. 2/2 doc: add another way to identify if a patch has been mergedKaartic Sivaraam, Aug 1, 2017
  16. Stefan BellerAug 1, 2017
  17. Kaartic SivaraamAug 2, 2017
  18. Junio C HamanoAug 2, 2017
  19. Junio C HamanoAug 2, 2017
  20. Stefan BellerAug 2, 2017
  21. Kaartic SivaraamAug 7, 2017
  22. Kaartic SivaraamAug 7, 2017
  23. Philip OakleyAug 1, 2017

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.