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

On Tue, 2017-08-01 at 10:46 -0700, Stefan Beller wrote:

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?

[1 ]https://public-inbox.org/git/CA+dzEB=cDvp7ZS8x+p+U-5NbK3SNd0FPyj_wP=gvi8mJi6D2ag@mail.gmail.com/

quoted

--
2.14.0.rc1.434.g6eded367a

-- 
Kaartic