public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: khc@pm.waw.pl
Cc: bunk@kernel.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Please pull - generic HDLC
Date: Mon, 13 Oct 2008 11:23:09 -0700 (PDT)	[thread overview]
Message-ID: <20081013.112309.129955744.davem@davemloft.net> (raw)
In-Reply-To: <m31vyk4kde.fsf@maximus.localdomain>

From: Krzysztof Halasa <khc@pm.waw.pl>
Date: Mon, 13 Oct 2008 16:53:17 +0200

> Adrian Bunk <bunk@kernel.org> writes:
> 
> > The over 3 weeks old -next already contains mostly the same as the HDLC 
> > tree contains now.
> >
> > The thing you two should sort out is why the tree ended up as an own 
> > tree in -next instead of pull requests to David long ago.
> >
> > E.g. the netdev and wireless trees also don't go into -next, but instead 
> > with frequent pull requests to David.
> 
> I can't see any problem with this, is there any?
> 
> I want the HDLC tree tested in next before it's merged upstream
> (= David's tree(s)). I don't want to push crap upstream  first and
> only then try to fix it (though a bug still slips in sometimes).

You're supposed to have your changes merged into the relevant
subsystem tree long before Linus's merge window opens up.

That's how it is meant to work.

What I'm doing with networking is nothing special.

So please be punctual and merge early and often to Jeff and
myself, so that you don't miss the merge window in the future.

      reply	other threads:[~2008-10-13 18:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-12 21:12 Please pull - generic HDLC Krzysztof Halasa
2008-10-12 21:47 ` David Miller
2008-10-12 22:35   ` Krzysztof Halasa
2008-10-13  5:53   ` Adrian Bunk
2008-10-13 14:53     ` Krzysztof Halasa
2008-10-13 18:23       ` David Miller [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=20081013.112309.129955744.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=bunk@kernel.org \
    --cc=khc@pm.waw.pl \
    --cc=linux-kernel@vger.kernel.org \
    --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