From: Jakub Kicinski <kuba@kernel.org>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: Tedd Ho-Jeong An <hj.tedd.an@gmail.com>,
David Miller <davem@davemloft.net>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
"open list:NETWORKING [GENERAL]" <netdev@vger.kernel.org>
Subject: Re: pull request: bluetooth-next 2022-07-22
Date: Tue, 26 Jul 2022 19:47:23 -0700 [thread overview]
Message-ID: <20220726194723.717ea49a@kernel.org> (raw)
In-Reply-To: <CABBYNZJoAe+XDp_Zq4bfepizxpmUiB_Vo-ix1A2TyJXjzQVe+Q@mail.gmail.com>
On Tue, 26 Jul 2022 18:06:47 -0700 Luiz Augusto von Dentz wrote:
> > No strong preference here as long as we can keep the sign-offs etc in
> > control. Note that I'm not aware of any other tree we pull rebasing,
> > tho, so you may run into unique issues.
>
> Maybe I need to get in touch with other maintainers to know what they
> are doing, but how about net-next, how does it gets updated? Is that
> done via git merge or git pull alone is enough?
git pull, if you mean upstream trees making their wait into net-next.
And afterwards submitter does git pull --ff-only to update their tree.
next prev parent reply other threads:[~2022-07-27 2:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 20:54 pull request: bluetooth-next 2022-07-22 Luiz Augusto von Dentz
2022-07-22 23:55 ` Jakub Kicinski
2022-07-23 0:09 ` Luiz Augusto von Dentz
2022-07-23 0:19 ` Jakub Kicinski
2022-07-23 0:25 ` Luiz Augusto von Dentz
2022-07-23 0:50 ` Jakub Kicinski
2022-07-26 22:05 ` Luiz Augusto von Dentz
2022-07-26 22:31 ` Jakub Kicinski
2022-07-27 1:06 ` Luiz Augusto von Dentz
2022-07-27 2:47 ` Jakub Kicinski [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-07-23 0:22 Luiz Augusto von Dentz
2022-07-23 2:10 ` patchwork-bot+netdevbpf
2022-08-01 21:15 ` patchwork-bot+bluetooth
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=20220726194723.717ea49a@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=hj.tedd.an@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).