From: <doiggl@velocitynet.com.au>
To: reiserfs-devel <reiserfs-devel@vger.kernel.org>
Subject: Re: latest reiser4progs source code location
Date: Wed, 09 Jan 2013 19:17:00 +1100 [thread overview]
Message-ID: <e7d0647cc77f1f0696880b7854fc44a3@mail.velocitynet.com.au> (raw)
In-Reply-To: <CADW=+3nBqVwUgnW20eZ7VZfx2ZjMtFTFob_2rrm0HUawtpBGsA@mail.gmail.com>
On Tue, 8 Jan 2013 16:13:28 +0100, Dušan Čolić <dusanc@gmail.com>
wrote:
> On Jan 8, 2013 4:11 PM, <doiggl@velocitynet.com.au> wrote:
>>
>> Hello,
>> Question:
>> Is this the latest reiser4progs source code [1]
>>
>
> AFAIK yes
>> Does it have these patches applied to it [2]?
>
> No
>
>> Thanks Glenn
>>
>> [1]source code
>>
http://sourceforge.net/projects/reiser4/files/reiser4-utils/reiser4progs/
>> reiser4progs-1.0.7.tar.gz 2011-11-13 845.4 kB
>>
>> [2]
>> reiser4progs: Limit printing of label to the maximum of 16 chars
>> http://www.spinics.net/lists/reiserfs-devel/msg03366.html
>>
>> reiser4progs: Handle unprepped items by fsck
>> http://www.spinics.net/lists/reiserfs-devel/msg02247.html
>>
>> reiser4progs: patch to let reiser4progs compile with gcc-4.4
>> http://www.spinics.net/lists/reiserfs-devel/msg01327.html
>> http://www.spinics.net/lists/reiserfs-devel/msg01328.html
>>
>> old empty location:
>> http://www.kernel.org/pub/linux/utils/fs/reiser4/reiser4progs/
>>
>> Referenced from
>> http://www.spinics.net/lists/reiserfs-devel/msg01253.html
Hello,
Question
Can a list of missing patches which can be applied to reiser4progs be
supplied.
Thanks Glenn
--
To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2013-01-09 8:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 15:06 latest reiser4progs source code location doiggl
[not found] ` <CADW=+3nBqVwUgnW20eZ7VZfx2ZjMtFTFob_2rrm0HUawtpBGsA@mail.gmail.com>
2013-01-09 8:17 ` doiggl [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=e7d0647cc77f1f0696880b7854fc44a3@mail.velocitynet.com.au \
--to=doiggl@velocitynet.com.au \
--cc=reiserfs-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).