From: "Jörn Engel" <joern@logfs.org>
To: Daniel Walker <dwalker@fifo99.com>
Cc: Linus <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Please pull logfs tree for fixes
Date: Wed, 21 Apr 2010 16:24:56 +0200 [thread overview]
Message-ID: <20100421142456.GC18441@logfs.org> (raw)
In-Reply-To: <1271858963.2058.4.camel@m0nster>
On Wed, 21 April 2010 07:09:22 -0700, Daniel Walker wrote:
> On Wed, 2010-04-21 at 14:19 +0200, Jörn Engel wrote:
> > Another set of fixes. Two of them are security relevant. But given
> > that an attacker needs mount access and few people have logfs compiled
> > in, that's unlikely to be a huge issue.
> >
> > gc.c | 8 ++++++
> > journal.c | 29 ++++++++++++++---------
> > logfs.h | 15 ++++++++++--
> > readwrite.c | 75 +++++++++++++++++++++++++++++++++---------------------------
> > segment.c | 8 ------
> > super.c | 11 +++++++-
> > 6 files changed, 91 insertions(+), 55 deletions(-)
>
> Where is the url for your tree? There's a git command,
Doh!
git://git.kernel.org/pub/scm/linux/kernel/git/joern/logfs.git
> "git request-pull"
>
> It spits out a form email with url , and all the needed info.
Nice. Guess I'll use that from now on. Thanks!
Jörn
--
"Translations are and will always be problematic. They inflict violence
upon two languages." (translation from German)
next prev parent reply other threads:[~2010-04-21 14:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-21 12:19 Please pull logfs tree for fixes Jörn Engel
2010-04-21 14:09 ` Daniel Walker
2010-04-21 14:24 ` Jörn Engel [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-05-17 17:19 Jörn Engel
2010-05-17 20:54 ` Linus Torvalds
2010-03-06 21:04 Please pull logfs tree Jörn Engel
2010-03-30 7:22 ` Please pull logfs tree for fixes Jörn Engel
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=20100421142456.GC18441@logfs.org \
--to=joern@logfs.org \
--cc=dwalker@fifo99.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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