From: Zach Brown <zach.brown@oracle.com>
To: Chris Mason <chris.mason@oracle.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Btrfs git repos available
Date: Thu, 25 Sep 2008 14:25:11 -0700 [thread overview]
Message-ID: <48DC01B7.50408@oracle.com> (raw)
In-Reply-To: <1222376788.7028.83.camel@think.oraclecorp.com>
> Well, after some hints from Linus I've rebased these about 4 times now.
> The new changesets are generally cleaner and are setup properly under
> fs/btrfs.
Can you publish these hints somewhere?
- z
next prev parent reply other threads:[~2008-09-25 21:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-24 19:02 Btrfs git repos available Chris Mason
2008-09-25 21:06 ` Chris Mason
2008-09-25 21:25 ` Zach Brown [this message]
2008-09-26 1:08 ` Chris Mason
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=48DC01B7.50408@oracle.com \
--to=zach.brown@oracle.com \
--cc=chris.mason@oracle.com \
--cc=linux-btrfs@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