netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarek Poplawski <jarkao2@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: READ ME, net-2.6 fully merged
Date: Sat, 19 Jul 2008 09:50:36 +0200	[thread overview]
Message-ID: <48819CCC.8070800@gmail.com> (raw)
In-Reply-To: <20080718.033947.193705552.davem@davemloft.net>

David Miller wrote, On 07/18/2008 12:39 PM:

> I merged Linus's current tree into net-next-2.6, fixed up all
> the merge conflicts, and pushed this out as plain "net-2.6":
> 
> 	master.kernel.org:/pub/scm/linux/kernel/git/davem/net-2.6.git
> 
> There is a net-next-2.6 still there, but it's just a plain clone
> of Linus's tree so that the linux-next folks can still do dummy
> pulls from it.

A little btw. question: I know you are busy now with more serious
problems and it's not for now, but: after the last net-next-2.6 git
policy change most of the time neither net-2.6 nor net-next-2.6
could be treated as current net state. I tried to stick to net-next,
but it was idle most of the time.

Isn't it possible to create the third git tree maintained the old
net-next way i.e. net-next-2.6 with immediate bug fixes from net-2.6
(and of course rebased from time to time)? I guess you could be doing
something like this privately, so it's not necessarily a lot of
additional hassle?

Thanks,
Jarek P.

  parent reply	other threads:[~2008-07-19  7:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-18 10:39 READ ME, net-2.6 fully merged David Miller
2008-07-18 16:51 ` Ben Hutchings
2008-07-18 17:05   ` [PATCH] e1000: resolve tx multiqueue bug Ben Hutchings
2008-07-19  0:04     ` Jeff Kirsher
2008-07-19  0:51       ` David Miller
2008-07-18 21:16   ` READ ME, net-2.6 fully merged David Miller
2008-07-18 22:43     ` Jeff Kirsher
2008-07-19  7:50 ` Jarek Poplawski [this message]
2008-07-19  8:01   ` David Miller

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=48819CCC.8070800@gmail.com \
    --to=jarkao2@gmail.com \
    --cc=davem@davemloft.net \
    --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).