netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Paul Mackerras <paulus@samba.org>
Cc: akpm@osdl.org, davem@davemloft.net, netdev@oss.sgi.com
Subject: Re: [PATCH] PPP multilink fragmentation improvements
Date: Thu, 31 Mar 2005 00:25:25 -0500	[thread overview]
Message-ID: <424B89C5.7000504@pobox.com> (raw)
In-Reply-To: <16971.34960.136639.262614@cargo.ozlabs.ibm.com>

Paul Mackerras wrote:
> Jeff Garzik writes:
> 
> 
>>Let me know when you feel comfortable to let it go upstream...
> 
> 
> I'm comfortable about it now, I just said -mm because I thought we
> were into the -rc phase in mainline (silly me :).

Yes, indeed...  since it's not strictly a bugfix, I would prefer to push 
it upstream after -rc cycle ends.

Unless I hear loud screaming, that's what I will do... :)

	Jeff

      reply	other threads:[~2005-03-31  5:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-30  4:56 [PATCH] PPP multilink fragmentation improvements Paul Mackerras
2005-03-31  0:45 ` Jeff Garzik
2005-03-31  5:20   ` Paul Mackerras
2005-03-31  5:25     ` Jeff Garzik [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=424B89C5.7000504@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=akpm@osdl.org \
    --cc=davem@davemloft.net \
    --cc=netdev@oss.sgi.com \
    --cc=paulus@samba.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).