From: James Bottomley <James.Bottomley@SteelEye.com>
To: Andrew Morton <akpm@osdl.org>, dwmw2@infradead.org
Cc: Andries Brouwer <Andries.Brouwer@cwi.nl>,
chrisw@osdl.org, aebr@win.tue.nl,
"Randy.Dunlap" <rddunlap@osdl.org>, Greg KH <greg@kroah.com>,
joecool1029@gmail.com,
SCSI Mailing List <linux-scsi@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Empty partition nodes not created (was device node issues with recent mm's and udev)
Date: Fri, 06 May 2005 09:12:47 -0500 [thread overview]
Message-ID: <1115388767.4989.2.camel@mulgrave> (raw)
In-Reply-To: <20050506020518.0b0afdc3.akpm@osdl.org>
On Fri, 2005-05-06 at 02:05 -0700, Andrew Morton wrote:
> > Should it be backed out of 2.6.11.8? Possibly - but if it will be
> > part of 2.6.12 or 2.6.13 then I would be inclined to leave it.
> >
> > Andrew asks whether it should be removed from -mm.
>
> It was merged into Linus's tree on March 8th (via bk, thank gawd. How do
> you find out that sort of info using git? Generating a full log is
> cheating).
Well, moving offtopic, but it is of relevance to people who use git.
The answer is that the information exists (we can use the commit tree to
reconstruct the file data) but that no-one has yet come up with a file
history viewing tool. I think David Woodhouse is the closest to
producing one of these, David?
James
next prev parent reply other threads:[~2005-05-06 14:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d4757e6005050219514ece0c0a@mail.gmail.com>
2005-05-03 3:14 ` Empty partition nodes not created (was device node issues with recent mm's and udev) Greg KH
2005-05-03 3:26 ` Randy.Dunlap
2005-05-03 4:18 ` Joe
2005-05-03 5:16 ` Randy.Dunlap
2005-05-06 8:04 ` Andries Brouwer
2005-05-06 16:43 ` Bryan Henderson
2005-05-03 10:55 ` Paulo Marques
2005-05-03 23:34 ` Joe
2005-05-06 8:00 ` Andries Brouwer
2005-05-06 8:10 ` Chris Wright
2005-05-06 8:43 ` Andries Brouwer
2005-05-06 9:05 ` Andrew Morton
2005-05-06 14:12 ` James Bottomley [this message]
2005-05-06 14:26 ` David Woodhouse
2005-05-06 14:34 ` Kay Sievers
2005-05-06 14:18 ` Kay Sievers
2005-05-06 15:50 ` Greg KH
2005-05-06 7:58 ` Andries Brouwer
[not found] <3ZVNP-5cq-7@gated-at.bofh.it>
[not found] ` <E1DTAgo-0002uD-F0@be1.7eggert.dyndns.org>
2005-05-04 3:49 ` Joe
2005-05-04 4:47 ` Grant Coady
2005-05-04 11:42 ` Bodo Eggert
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=1115388767.4989.2.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=Andries.Brouwer@cwi.nl \
--cc=aebr@win.tue.nl \
--cc=akpm@osdl.org \
--cc=chrisw@osdl.org \
--cc=dwmw2@infradead.org \
--cc=greg@kroah.com \
--cc=joecool1029@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=rddunlap@osdl.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