From: Randy Dunlap <rdunlap@xenotime.net>
To: Sergiu Iordache <sergiu@google.com>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
marco.stornelli@gmail.com
Subject: Re: [PATCH] char drivers: ramoops documentation
Date: Mon, 1 Aug 2011 17:19:19 -0700 [thread overview]
Message-ID: <20110801171919.307cd945.rdunlap@xenotime.net> (raw)
In-Reply-To: <CAGDaqBSrbH4JV0xS8YHedy1H6O86rk0HLxjtd15C0-GchsNOvg@mail.gmail.com>
On Mon, 1 Aug 2011 15:37:49 -0700 Sergiu Iordache wrote:
> On Mon, Aug 1, 2011 at 3:05 PM, Randy Dunlap <rdunlap@xenotime.net> wrote:
> > On Mon, 1 Aug 2011 14:26:50 -0700 Sergiu Iordache wrote:
> >
> >> Add a documentation file describing the usage of Ramoops
> >>
> >> Change-Id: I9dab9c4b9e4921b220574470372e330d32f9c63b
> >
> > eh?
> Sorry, was it the commit message you did not like or something else?
The "Change-Id:" line.
There was a discussion that began with a July 14 patch from Mike Waychison
<mikew@google.com>:
Subject: [PATCH 1/2] Kconfig: Allow disabling of CONFIG_DEVPORT
that included the line:
Google-Bug-Id: 3177114
Basically we don't want umpteen zillion different such tags in commit
messages. I posted a patch last Friday:
Subject: [PATCH] Documentation: add Internal-reference-ID: patch tag
that allows people who want to track their internal references in commit
messages to use a common tag label/format:
Internal-reference-ID: <text>
<text> should not be a private (internal) URL.
> Thanks, I've updated the doc using your feedback. I have also
> rearranged the "1. Ramoops concepts" part to make it look better I
> think. I'll wait a bit for some more comments and then resubmit the
> new version of the patch.
Thanks.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2011-08-02 0:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-01 21:26 Sergiu Iordache
2011-08-01 22:05 ` Randy Dunlap
2011-08-01 22:37 ` Sergiu Iordache
2011-08-02 0:19 ` Randy Dunlap [this message]
2011-08-05 23:33 Sergiu Iordache
2011-08-07 1:25 ` 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=20110801171919.307cd945.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marco.stornelli@gmail.com \
--cc=sergiu@google.com \
/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
all inboxes | Powered by JetHome®