From: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Petr Mladek <pmladek@suse.com>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
"Paul E. McKenney" <paulmck@linux.ibm.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Liu Chuansheng <chuansheng.liu@intel.com>,
Valdis Kletnieks <valdis.kletnieks@vt.edu>,
linux-kernel@vger.kernel.org, Dmitry Vyukov <dvyukov@google.com>
Subject: Re: [PATCH] kernel/hung_task.c: Monitor killed tasks.
Date: Wed, 22 May 2019 23:58:12 +0900 [thread overview]
Message-ID: <03b5834d-5f8f-9c7e-20df-cfdf5395d245@i-love.sakura.ne.jp> (raw)
In-Reply-To: <20190522234134.44327256@canb.auug.org.au>
On 2019/05/22 22:41, Stephen Rothwell wrote:
> Hi Tetsuo,
>
> On Wed, 22 May 2019 21:38:45 +0900 Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp> wrote:
>>
>> I want to send debug printk() patches to linux-next.git. Petr Mladek
>> is suggesting me to have a git tree for debug printk() patches.
>> But it seems that there is "git quiltimport" command, and I prefer
>> "subversion + quilt", and I don't have trees for sending "git pull"
>> requests. Therefore, just ignoring "git quiltimport" failure is fine.
>> What do you think?
>
> Sure, we can try. I already have one quilt tree (besides Andrew's) in
> linux-next, but much prefer a git tree. If you have to use a quilt
> tree, I will import it into a local branch on the base you tell me to
> and then fetch it every morning and reimport it if it changes. I will
> then merge it like any other git branch. Let me know what you can deal
> with.
>
What I do for making patches is:
git fetch --tags
git reset --hard next-$date
edit files
git commit -a -s
git format-patch -1
git send-email --to=$recipient 0001-*.patch
I'm sure I will confuse git history/repository everyday if
I try to send changes using git. For my skill level, managing
0001-*.patch in a subversion repository is the simplest and safest.
next prev parent reply other threads:[~2019-05-22 15:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-13 11:02 [PATCH] kernel/hung_task.c: Monitor killed tasks Tetsuo Handa
2019-05-13 11:11 ` Dmitry Vyukov
2019-05-14 22:28 ` Paul E. McKenney
2019-05-15 10:55 ` Petr Mladek
2019-05-16 8:19 ` Tetsuo Handa
2019-05-16 11:57 ` Petr Mladek
2019-05-16 12:38 ` Tetsuo Handa
2019-05-22 12:38 ` Tetsuo Handa
2019-05-22 13:41 ` Stephen Rothwell
2019-05-22 14:58 ` Tetsuo Handa [this message]
2019-05-22 21:09 ` Tetsuo Handa
2019-05-22 21:39 ` Stephen Rothwell
2019-05-22 21:43 ` Andrew Morton
2019-05-22 23:46 ` Tetsuo Handa
2019-05-27 14:12 ` Tetsuo Handa
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=03b5834d-5f8f-9c7e-20df-cfdf5395d245@i-love.sakura.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=akpm@linux-foundation.org \
--cc=chuansheng.liu@intel.com \
--cc=dvyukov@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulmck@linux.ibm.com \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=sfr@canb.auug.org.au \
--cc=valdis.kletnieks@vt.edu \
--cc=vkuznets@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.