From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
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: Thu, 23 May 2019 07:39:25 +1000 [thread overview]
Message-ID: <20190523073925.169563ed@canb.auug.org.au> (raw)
In-Reply-To: <abbfb5df-40da-63c8-0333-805083397533@i-love.sakura.ne.jp>
[-- Attachment #1: Type: text/plain, Size: 1101 bytes --]
Hi Tetsuo,
On Thu, 23 May 2019 06:09:07 +0900 Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp> wrote:
>
> > 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.
> >
>
> I put an example patch into my subversion repository:
>
> svn checkout https://svn.osdn.net/svnroot/tomoyo/branches/syzbot-patches/
>
> To fetch up-to-date debug printk() patches:
>
> cd syzbot-patches
> svn update
>
> Does this work for you?
Neither will fit into my normal workflow.
So, tell me, what are you trying to do? What does you work depend on?
Just Linus' tree, or something already in linux-next? Why would you
want to keep moving your patch(es) on top of linux-next?
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-05-22 21:39 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
2019-05-22 21:09 ` Tetsuo Handa
2019-05-22 21:39 ` Stephen Rothwell [this message]
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=20190523073925.169563ed@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--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=penguin-kernel@i-love.sakura.ne.jp \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--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.