From: Linus Torvalds <torvalds@linux-foundation.org>
To: "Jörn Engel" <joern@logfs.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: Please pull logfs tree
Date: Sat, 6 Mar 2010 14:04:18 -0800 (PST) [thread overview]
Message-ID: <alpine.LFD.2.00.1003061403110.31447@localhost.localdomain> (raw)
In-Reply-To: <20100306213501.GB21570@logfs.org>
On Sat, 6 Mar 2010, Jörn Engel wrote:
>
> Ok, learned something new again. Thank you for doing the trivial merge
> that would have taken me days to figure out. :)
Heh. I do those things day in and day out. That was a really easy merge.
And I'm happy you pointed it out beforehand, so that we didn't get a
separate commit and non-bisectable history.
Linus
next prev parent reply other threads:[~2010-03-06 22:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-06 21:04 Please pull logfs tree Jörn Engel
2010-03-06 21:26 ` Linus Torvalds
2010-03-06 21:35 ` Jörn Engel
2010-03-06 22:04 ` Linus Torvalds [this message]
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=alpine.LFD.2.00.1003061403110.31447@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=joern@logfs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.