All of lore.kernel.org
 help / color / mirror / Atom feed
From: prasad <prasadjoshi.linux@gmail.com>
To: prasad <prasadjoshi.linux@gmail.com>
Cc: tristan.lelong@blunderer.org,
	Artem Bityutskiy <dedekind1@gmail.com>,
	Joern Engel <joern@logfs.org>,
	logfs@logfs.org, linux-mtd@lists.infradead.org,
	linux-fsdevel@vger.kernel.org
Subject: Re: make offline logfs image and some BUG()
Date: Thu, 22 Nov 2012 22:29:27 +0530	[thread overview]
Message-ID: <50ae59ff.29bf440a.1489.ffffc522@mx.google.com> (raw)
In-Reply-To: <50ae5961.08ef440a.0ab6.ffffcafe@mx.google.com>

On Thu, Nov 22, 2012 at 10:26:53PM +0530, prasad wrote:
> On Thu, Nov 22, 2012 at 12:53:58PM +0200, Artem Bityutskiy wrote:
> > On Mon, 2012-11-19 at 14:31 -0500, Tristan Lelong wrote:
> > > Hi,
> > > 
> > > I am trying to use logfs for a project I am currently working on. The 
> > > kernel version I used is 2.6.37 with some patch from TI DM8168.
> > 
> > I wonder if logfs is maintained?
> 
> It is being maintained however, for last few months I have not been able to work on it much.

BTW,
The latest repository is here https://github.com/prasad-joshi/logfs_upstream

> 
> > 
> > -- 
> > Best Regards,
> > Artem Bityutskiy
> 
> 

WARNING: multiple messages have this Message-ID (diff)
From: prasad <prasadjoshi.linux@gmail.com>
To: prasad <prasadjoshi.linux@gmail.com>
Cc: tristan.lelong@blunderer.org,
	Artem Bityutskiy <dedekind1@gmail.com>,
	Joern Engel <joern@logfs.org>,
	logfs@logfs.org, linux-mtd@lists.infradead.org,
	linux-fsdevel@vger.kernel.org
Subject: Re: make offline logfs image and some BUG()
Date: Thu, 22 Nov 2012 22:29:27 +0530	[thread overview]
Message-ID: <50ae59ff.29bf440a.1489.ffffc522@mx.google.com> (raw)
In-Reply-To: <50ae5961.08ef440a.0ab6.ffffcafe@mx.google.com>

On Thu, Nov 22, 2012 at 10:26:53PM +0530, prasad wrote:
> On Thu, Nov 22, 2012 at 12:53:58PM +0200, Artem Bityutskiy wrote:
> > On Mon, 2012-11-19 at 14:31 -0500, Tristan Lelong wrote:
> > > Hi,
> > > 
> > > I am trying to use logfs for a project I am currently working on. The 
> > > kernel version I used is 2.6.37 with some patch from TI DM8168.
> > 
> > I wonder if logfs is maintained?
> 
> It is being maintained however, for last few months I have not been able to work on it much.

BTW,
The latest repository is here https://github.com/prasad-joshi/logfs_upstream

> 
> > 
> > -- 
> > Best Regards,
> > Artem Bityutskiy
> 
> 

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2012-11-22 16:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-19 19:31 make offline logfs image and some BUG() Tristan Lelong
2012-11-22 10:53 ` Artem Bityutskiy
2012-11-22 10:53   ` Artem Bityutskiy
2012-11-22 16:56   ` prasad
2012-11-22 16:56     ` prasad
2012-11-22 16:59     ` prasad [this message]
2012-11-22 16:59       ` prasad

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=50ae59ff.29bf440a.1489.ffffc522@mx.google.com \
    --to=prasadjoshi.linux@gmail.com \
    --cc=dedekind1@gmail.com \
    --cc=joern@logfs.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=logfs@logfs.org \
    --cc=tristan.lelong@blunderer.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 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.