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