All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, pabeni@redhat.com, alex.aring@gmail.com,
	stefan@datenfreihafen.org, netdev@vger.kernel.org,
	linux-wpan@vger.kernel.org
Subject: Re: pull-request: ieee802154 for net-next 2023-06-23
Date: Mon, 26 Jun 2023 12:39:57 +0200	[thread overview]
Message-ID: <20230626123957.2f9bb4c9@xps-13> (raw)
In-Reply-To: <20230624155947.1b94903e@kernel.org>

Hi Jakub,

kuba@kernel.org wrote on Sat, 24 Jun 2023 15:59:47 -0700:

> On Fri, 23 Jun 2023 19:55:06 +0200 Miquel Raynal wrote:
> > As you know, we are trying to build a wpan maintainers group so here is
> > my first ieee802154 pull-request for your *net-next* tree.  
> 
> Pulled thanks!
> 
> In the future, please try to avoid merging in tags from Linus's tree
> directly. You can send a PR to net-next and fast forward, that results
> in a more straightforward shape of the history, and avoids getting 
> the back-merging wrong (Linus said a couple of times that any cross-
> -merge must have an explanation in the commit message, for example).

I agree merging upstream tags darkens the history. So IIUC, it's fine
to have an -rc tag higher than -rc1 as base, but you prefer to receive
one merge request per "base tag". Duly noted.

Thanks!
Miquèl

      reply	other threads:[~2023-06-26 10:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-23 17:55 pull-request: ieee802154 for net-next 2023-06-23 Miquel Raynal
2023-06-24 22:59 ` Jakub Kicinski
2023-06-26 10:39   ` Miquel Raynal [this message]

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=20230626123957.2f9bb4c9@xps-13 \
    --to=miquel.raynal@bootlin.com \
    --cc=alex.aring@gmail.com \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=linux-wpan@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=stefan@datenfreihafen.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 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.