From: Dave Jones <davej@suse.de>
To: Oleg Drokin <green@namesys.com>
Cc: Sebastian Dr?ge <sebastian.droege@gmx.de>,
linux-kernel@vger.kernel.org, Andrew Morton <akpm@zip.com.au>
Subject: Re: Current Reiserfs Update / 2.5.2-dj7 Oops
Date: Thu, 31 Jan 2002 14:11:01 +0100 [thread overview]
Message-ID: <20020131141101.B5948@suse.de> (raw)
In-Reply-To: <20020130151420.40e81aef.sebastian.droege@gmx.de> <20020130173715.B2179@namesys.com> <20020130163951.13daca94.sebastian.droege@gmx.de> <20020130190905.A820@namesys.com> <20020130174011.L24012@suse.de> <20020130201054.6e150f78.sebastian.droege@gmx.de> <20020130201757.Q24012@suse.de> <20020131122424.A874@namesys.com> <20020131134931.A5948@suse.de> <20020131155325.A3629@namesys.com>
In-Reply-To: <20020131155325.A3629@namesys.com>; from green@namesys.com on Thu, Jan 31, 2002 at 03:53:25PM +0300
On Thu, Jan 31, 2002 at 03:53:25PM +0300, Oleg Drokin wrote:
> > One possible is that I've goofed whilst merging Andrew Mortons
> > "out of disk space during truncate" fixes from 2.4. Andrew, could
> > have a quick scan through the fs/ changes in -dj6 and see if anything
> > jumps out at you ?
> Hm, but I remember dj6 was reported as "working"?
-ENOTAWAKEYET. Yes, I meant -dj7 there. oops.
> > I'll take a look myself later too, but right now, it's a head-scratcher.
> Do you have some place where one can see all separate patches 2.5.2-dj7
> consist of?
I keep a directory named after each revision, patches get dumped there
as I merge them, and also I dump bits of ~/Mail/merged there.
These patches however are not always identical to what gets merged,
as they sometimes need to be bent into shape to live with something
else that got merged, I hand-edit the diffs to make them apply,
sometimes removing complete hunks, and grafting that hunks intention
into place in the source instead.
So they're of little use to anyone in their current state, given that
there are 'holes' where I chopped bits out. Sometimes I rediff the
patch afterwards, but not always.
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2002-01-31 13:11 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-30 14:14 Current Reiserfs Update / 2.5.2-dj7 Oops Sebastian Dröge
2002-01-30 14:37 ` Oleg Drokin
2002-01-30 15:39 ` Sebastian Dröge
2002-01-30 16:09 ` Oleg Drokin
2002-01-30 16:40 ` Dave Jones
2002-01-30 16:44 ` Oleg Drokin
2002-01-30 16:55 ` Dave Jones
2002-01-30 17:07 ` Oleg Drokin
2002-01-30 19:10 ` Sebastian Dröge
2002-01-30 19:17 ` Dave Jones
2002-01-31 6:09 ` Oleg Drokin
2002-01-31 9:24 ` Oleg Drokin
2002-01-31 12:49 ` Dave Jones
2002-01-31 12:53 ` Oleg Drokin
2002-01-31 13:11 ` Dave Jones [this message]
2002-01-31 16:44 ` Oleg Drokin
2002-01-31 17:23 ` Sebastian Dröge
2002-01-31 17:45 ` Chris Mason
-- strict thread matches above, loose matches on Subject: below --
2002-01-31 10:10 Martin Bahlinger
2002-01-31 13:03 ` Oleg Drokin
2002-01-31 17:20 ` Martin Bahlinger
2002-01-31 17:44 Martin Bahlinger
2002-01-31 20:44 ` Martin Bahlinger
2002-02-01 5:55 ` Oleg Drokin
2002-02-01 22:17 ` Martin Bahlinger
2002-02-02 8:30 ` Oleg Drokin
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=20020131141101.B5948@suse.de \
--to=davej@suse.de \
--cc=akpm@zip.com.au \
--cc=green@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sebastian.droege@gmx.de \
/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