linux-kernel - Re: [PATCH] SubmittingPatches: add git pull & diffstat format info

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <488DF88D.4020003@s5r6.in-berlin.de>
Date:	Mon, 28 Jul 2008 18:49:17 +0200
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	Randy Dunlap <randy.dunlap@...cle.com>
CC:	lkml <linux-kernel@...r.kernel.org>,
	torvalds <torvalds@...ux-foundation.org>,
	akpm <akpm@...ux-foundation.org>
Subject: Re: [PATCH] SubmittingPatches: add git pull & diffstat format info

Randy Dunlap wrote:
> On Mon, 28 Jul 2008 13:29:00 +0200 Stefan Richter wrote:
>> Isn't SubmittingPatches the wrong text for this?
> 
> Is there a good place for it?

I am alas not aware of a well fitting place.

But I see that it was already committed.  Hence a sentence should be
added about whether/when/what for to publish proposed changes in a git tree.

> Thanks for the feedback.

Here is some more, after the fact:

  - The two points that you are making...

      (a) The repo URL should be convenient for cut'n'paste, i.e.
      complete with protocol specifier like git:// and followed by the
      branch name from which to pull, without line break between them.
      (b) Include a shortlog and a diffstat generated by "git diff -M
      --stat --summary".  This properly shows file renames, creations,
      deletions.

   ...can be told with far fewer words.

  - You could mention that 'git request-pull' can be used to generate
    the message text.

  - Since this was placed in SubmittingPatches (targeted to submitters
    rather than subsystem maintainers), it surely is noteworthy that a
    pull request or announcement of a repo should sufficiently explain
    the purpose of the repo or request, including its status WRT testing
    and review, similar to a "[patch 0/n]" post.

PS:  SubmittingPatches doesn't mention the "do"s and "don't"s of [patch
0/n] posts yet...
-- 
Stefan Richter
-=====-==--- -=== ===--
http://arcgraph.de/sr/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/