From: "Theodore Ts'o" <tytso@mit.edu>
To: Viacheslav Dubeyko <Slava.Dubeyko@ibm.com>
Cc: "glaubitz@physik.fu-berlin.de" <glaubitz@physik.fu-berlin.de>,
"frank.li@vivo.com" <frank.li@vivo.com>,
"slava@dubeyko.com" <slava@dubeyko.com>,
"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: Fri, 2 May 2025 08:52:55 -0400 [thread overview]
Message-ID: <20250502125255.GA333135@mit.edu> (raw)
In-Reply-To: <72b00e25d492fff6f457779a73ef8bc737467b39.camel@ibm.com>
On Thu, May 01, 2025 at 07:48:35PM +0000, Viacheslav Dubeyko wrote:
> > 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.
Pro tip: If you are using "b4 am" to download patches from
lore.kernel.org, use the -c option, e.g., "b4 am -c [msgid]". This
will automatically check to make sure the patches have valid DKIM
headers, etc. and will also check to see if there is a newer version
of the patch series on lore.kernel.org and download it instead.
Another cool command is "b4 shazaam"; see the b4 man page for more details.
> > 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.
If you have a fork of the kernel tree, sure, you can just use that and
tell folks what branch they should look at.
Github should be just fine creating another fork of the kernel tree,
however. One advantage of having separate forks is that once you set
up the kernel.org tree from your local git tree, it becomes easier to
update multiple trees via separate git trees. So for example, when I
push out changes, I might do
git push ra # ra.kernel.org is a CNAME for gitolite.kernel.org
# and is easier to type. :-)
git push github
... and this will update my trees on kernel.org and github
automatically, aince I have in my .git/config file:
[remote "ra"]
url = ssh://gitolite@ra.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git
fetch = +refs/heads/*:refs/remotes/ext4/*
push = +master:master
push = +origin:origin
push = +fixes:fixes
push = +dev:dev
push = +test:test
[remote "github"]
url = git@github.com:tytso/ext4.git
fetch = +refs/heads/*:refs/remotes/github/*
push = +master:master
push = +origin:origin
push = +fixes:fixes
push = +dev:dev
push = +test:test
Cheers,
- Ted
next prev parent reply other threads:[~2025-05-02 12:53 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
2025-05-02 12:52 ` Theodore Ts'o [this message]
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=20250502125255.GA333135@mit.edu \
--to=tytso@mit.edu \
--cc=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 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.