From: Ralf Baechle <ralf@linux-mips.org>
To: Pete Popov <ppopov@embeddedalley.com>
Cc: Sergei Shtylylov <sshtylyov@ru.mvista.com>,
Linux MIPS Development <linux-mips@linux-mips.org>
Subject: Re: [Fwd: mtd/drivers/mtd/nand au1550nd.c,1.13,1.14]
Date: Tue, 15 Nov 2005 15:24:37 +0000 [thread overview]
Message-ID: <20051115152437.GA15733@linux-mips.org> (raw)
In-Reply-To: <1131911400.11644.84.camel@localhost.localdomain>
On Sun, Nov 13, 2005 at 11:49:59AM -0800, Pete Popov wrote:
> On Sun, 2005-11-13 at 22:47 +0300, Sergei Shtylylov wrote:
> > Hello.
> >
> > Thought it's worth forwarding this here...
>
> Just FYI, the patch is in the mtd tree only right now. It will get to
> linux-mips when Ralf does a pull.
(This is less a direct comment to you posting than a general advice to
people about what's going on in the git archive ...)
On the master (that is 2.6) branch I'm doing that about once a day.
This also means people are living dangerous if checking out the head of
the master branch. Who doesn't want to participate in debugging all this
mess is probably better or to checkout one of the tagged releases.
Also not that Linus only change the version number in the Makefile when
he does a release. That means for example until he releases 2.6.14-rc1
the Makefile will still say 2.6.14 - even though the diff may be huge,
well above 150,000 lines in this case.
Ralf
prev parent reply other threads:[~2005-11-15 15:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-13 19:47 [Fwd: mtd/drivers/mtd/nand au1550nd.c,1.13,1.14] Sergei Shtylylov
2005-11-13 19:49 ` Pete Popov
2005-11-13 19:55 ` Sergei Shtylylov
2005-11-15 15:24 ` Ralf Baechle [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=20051115152437.GA15733@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=ppopov@embeddedalley.com \
--cc=sshtylyov@ru.mvista.com \
/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