From: David Woodhouse <dwmw2@infradead.org>
To: "Jeremy Jackson" <jerj@coplanar.net>
Cc: linux-mtd@lists.infradead.org, dmwm2@infradead.org
Subject: Re: patch solving the wrong prolem?
Date: Fri, 05 Apr 2002 23:57:29 +0100 [thread overview]
Message-ID: <25655.1018047449@redhat.com> (raw)
In-Reply-To: <006401c1dbff$4550c830$7e0aa8c0@bridge>
jerj@coplanar.net said:
> I guess I'm just trying to get in the loop... I could use some info
> on what gets released where, when, etc.
Mostly, the stuff in CVS is newer. Some people submit changes directly to
Linus without bothering to Cc me, and those patches tend to take a lot
longer to get merged. Periodically, I send the CVS code to Linus and/or
Marcelo. I did some of that recently, and there's more to come.
--
dwmw2
prev parent reply other threads:[~2002-04-05 22:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-04 17:36 patch solving the wrong prolem? Jeremy Jackson
2002-04-05 22:57 ` David Woodhouse [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=25655.1018047449@redhat.com \
--to=dwmw2@infradead.org \
--cc=dmwm2@infradead.org \
--cc=jerj@coplanar.net \
--cc=linux-mtd@lists.infradead.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