All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yury Umanets <umka@namesys.com>
To: Oleg Drokin <green@namesys.com>
Cc: Travis Crump <pretzalz@techhouse.org>,
	Marcel Weber <mmweber@ncpro.com>,
	Hans Reiser <reiser@namesys.com>,
	Vitaly Fertman <vitaly@namesys.com>,
	reiserfs-list@namesys.com, debian-testing@lists.debian.org,
	Ed Boraas <ed@debian.org>,
	debian-devel@lists.debian.org
Subject: Re: plagiarism of reiserfs by Debian
Date: Mon, 21 Apr 2003 12:47:40 +0400	[thread overview]
Message-ID: <3EA3B02C.9010303@namesys.com> (raw)
In-Reply-To: <20030421100315.A23789@namesys.com>

Oleg Drokin wrote:

>Hello!
>
>On Sat, Apr 19, 2003 at 03:05:16PM -0400, Travis Crump wrote:
>  
>
>>You mean a bug report like 
>><http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=152547>?  Oh, wait... 
>> What if someone wanted to write a gtk frontend to mkreiserfs?  The 
>>    
>>
>
>Last time we spoke with EVMS folks about this kind of stuff, we agreed that they'd open
>a pipe to mkreiserfs and then will show the mkreiserfs' output in separate window.
>(in fact not only mkreiserfs's output, but output of all tools they run).
>
>Flames to /dev/null.
>
>And there are (were?) another set of tools for making/modifying reiserfs filesystems
>(except that there is no fsck) called progsreiserfs. (not being developed anymore, I think, but it
>works as is). Use that, if you like it more.
>
>Bye,
>    Oleg
>
>
>  
>
It is developed yet, but more slowly than before :)

-- 
Yury Umanets
"We're flying high, we're watching the world passes by..."




  reply	other threads:[~2003-04-21  8:47 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-18 12:04 reiserfsck infinite loop at pass2 (built by Debian) Vitaly Fertman
2003-04-18 15:10 ` Dieter Nützel
2003-04-18 15:11   ` Oleg Drokin
2003-04-18 15:26     ` Dieter Nützel
2003-04-18 15:27       ` Oleg Drokin
2003-04-19 16:07 ` plagiarism of reiserfs by Debian Hans Reiser
2003-04-19 17:29   ` Ben Collins
2003-04-19 18:40     ` Jarno Elonen
2003-04-19 19:24     ` Matt Ryan
2003-04-19 20:56       ` Ben Collins
2003-04-20 19:39         ` Matt Ryan
2003-04-19 18:02   ` Marcel Weber
2003-04-19 19:05     ` Travis Crump
2003-04-19 20:55       ` Ben Collins
2003-04-19 21:13         ` Anders Widman
2003-04-19 21:09           ` Ben Collins
2003-04-19 22:25         ` Andreas Dilger
2003-04-19 23:06           ` Chris Cheney
2003-04-20  0:49             ` Marcel Weber
2003-04-20  3:41               ` Glenn Maynard
2003-04-20  6:17                 ` Manuel Krause
2003-04-20  6:44                   ` Manuel Krause
2003-04-22  2:28                 ` Anthony DeRobertis
2003-04-23 15:17                   ` Hans Reiser
2003-04-23 15:35                     ` Anthony DeRobertis
2003-04-23 20:10                     ` Adam Heath
2003-04-21  6:03       ` Oleg Drokin
2003-04-21  8:47         ` Yury Umanets [this message]
2003-04-19 18:30   ` Florian Weimer
2003-04-19 20:51     ` Lukas Geyer
2003-04-19 23:24       ` Wouter Verhelst
2003-04-21 18:49         ` Walter Landry
2003-04-22  1:15         ` Brian M. Carlson
2003-04-21 13:22     ` bscott
2003-04-20  1:18   ` Matt Zimmerman
2003-04-20  1:20     ` Matt Zimmerman
2003-04-20 11:42   ` Marcelo E. Magallon

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=3EA3B02C.9010303@namesys.com \
    --to=umka@namesys.com \
    --cc=debian-devel@lists.debian.org \
    --cc=debian-testing@lists.debian.org \
    --cc=ed@debian.org \
    --cc=green@namesys.com \
    --cc=mmweber@ncpro.com \
    --cc=pretzalz@techhouse.org \
    --cc=reiser@namesys.com \
    --cc=reiserfs-list@namesys.com \
    --cc=vitaly@namesys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.