mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
	torvalds <torvalds@linux-foundation.org>,
	akpm <akpm@linux-foundation.org>
Subject: Re: [PATCH] SubmittingPatches: add git pull & diffstat format info
Date: Mon, 28 Jul 2008 18:49:17 +0200	[thread overview]
Message-ID: <488DF88D.4020003@s5r6.in-berlin.de> (raw)
In-Reply-To: <20080728081158.5c8d6873.randy.dunlap@oracle.com>

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/

  reply	other threads:[~2008-07-28 16:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-28  3:44 Randy Dunlap
2008-07-28 11:29 ` Stefan Richter
2008-07-28 15:11   ` Randy Dunlap
2008-07-28 16:49     ` Stefan Richter [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-07-21 22:58 Randy Dunlap

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=488DF88D.4020003@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome