All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: kkeil@suse.de, isdn4linux@listserv.isdn4linux.de,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	davem@davemloft.net
Subject: Re: [for 2.6.26] ISDN cleanups, ok for upstream?
Date: Sun, 20 Apr 2008 18:20:01 -0400	[thread overview]
Message-ID: <480BC191.6030905@garzik.org> (raw)
In-Reply-To: <20080418164113.6863213d.akpm@linux-foundation.org>

Andrew Morton wrote:
> On Fri, 18 Apr 2008 18:53:55 -0400
> Jeff Garzik <jeff@garzik.org> wrote:
> 
>> I don't know the current state of
>> akpm's pull of jgarzik/misc-2.6.git#ALL.
> 
> oops.  It seems that I disabled it quite a long time ago.   I'll resurrect
> it.

Thanks!  Though note that it will be temporary empty, after 
isdn-cleanups is sent upstream.

If it's not too much trouble, I would appreciate you continuing to poll 
misc-2.6.git#ALL, even if it comes up empty.  That tree (and branch) 
acts as an outlet for miscellaneous jgarzik stuff that may go upstream 
"vaguely soonish maybe"  :)


>> The 'isdn-cleanups' branch of
>> master.kernel.org:/pub/scm/linux/kernel/git/jgarzik/misc-2.6.git isdn-cleanups
> 
> That merges cleanly against the small number of isdn patches which are
> pending in -mm, so we're OK from that POV.

Thanks for checking.

Regards,

	Jeff



  reply	other threads:[~2008-04-20 22:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-18 22:53 [for 2.6.26] ISDN cleanups, ok for upstream? Jeff Garzik
2008-04-18 23:41 ` Andrew Morton
2008-04-20 22:20   ` Jeff Garzik [this message]
2008-04-19  0:13 ` 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=480BC191.6030905@garzik.org \
    --to=jeff@garzik.org \
    --cc=akpm@linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=isdn4linux@listserv.isdn4linux.de \
    --cc=kkeil@suse.de \
    --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 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.