The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Viacheslav Dubeyko <Slava.Dubeyko@ibm.com>
To: "glaubitz@physik.fu-berlin.de" <glaubitz@physik.fu-berlin.de>,
	"frank.li@vivo.com" <frank.li@vivo.com>,
	"slava@dubeyko.com" <slava@dubeyko.com>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE:  回复:  [PATCH 1/2] hfsplus: fix to update ctime after rename
Date: Thu, 1 May 2025 19:48:35 +0000	[thread overview]
Message-ID: <72b00e25d492fff6f457779a73ef8bc737467b39.camel@ibm.com> (raw)
In-Reply-To: <082cd97a11ca1680249852e975f8c3e06b53c26c.camel@physik.fu-berlin.de>

On Thu, 2025-05-01 at 21:10 +0200, John Paul Adrian Glaubitz wrote:
> Hi Slava,
> 
> 

<skipped>

> > 
> > Does 'git apply' works on your side if you try to apply the patch from email? Is
> > it some glitch on my side? As far as I can see, I am trying to apply on clean
> > kernel tree.
> 
> git-apply is for applying plain patches while git-am is for patches from mailboxes.
> 
> I would suggest to always use git-am after fetching patches using "b4 am <MSGID>"
> from the kernel mailing list.
> 
> Please note that when you apply patches with git-am, you should always use the "-s"
> option so that the patches are automatically signed-off with your own email address.
> 

Sorry, my glitch. :)

> Btw, can you push your tree somewhere until you've got your kernel.org account?
> 

Do we really need to create some temporary tree? I have a fork of kernel tree on
github where I am managing SSDFS source code. But I am not sure that I can
create another fork of kernel tree on github.

Thanks,
Slava.



  reply	other threads:[~2025-05-01 19:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-29 20:15 [PATCH 1/2] hfsplus: fix to update ctime after rename Yangtao Li
2025-04-29 20:15 ` [PATCH 2/2] hfs: " Yangtao Li
2025-04-29 21:31   ` Viacheslav Dubeyko
2025-05-02  0:03   ` Viacheslav Dubeyko
2025-05-07 14:22     ` 回复: " 李扬韬
2025-05-09 17:51       ` Viacheslav Dubeyko
2025-05-09 19:02         ` Viacheslav Dubeyko
2025-05-10  5:31         ` 回复: " 李扬韬
2025-05-15  1:10           ` Viacheslav Dubeyko
2025-04-29 21:27 ` [PATCH 1/2] hfsplus: " Viacheslav Dubeyko
2025-05-01 12:01   ` 回复: " 李扬韬
2025-05-01 18:57     ` Viacheslav Dubeyko
2025-05-01 19:10       ` John Paul Adrian Glaubitz
2025-05-01 19:48         ` Viacheslav Dubeyko [this message]
2025-05-02 12:52           ` Theodore Ts'o
2025-05-05 22:31             ` Viacheslav Dubeyko
2025-05-02  0:07 ` Viacheslav Dubeyko

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=72b00e25d492fff6f457779a73ef8bc737467b39.camel@ibm.com \
    --to=slava.dubeyko@ibm.com \
    --cc=frank.li@vivo.com \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=slava@dubeyko.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