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@xxxxxxxxxxxxx/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@xxxxxxxxxx: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
