From: Josef Bacik <josef@redhat.com>
To: Daniel J Blueman <daniel.blueman@gmail.com>
Cc: Josef Bacik <josef@redhat.com>,
Chris Mason <chris.mason@oracle.com>,
Linux BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] mark internal functions static
Date: Tue, 12 Apr 2011 08:41:40 -0400 [thread overview]
Message-ID: <20110412124140.GA26337@dhcp231-156.rdu.redhat.com> (raw)
In-Reply-To: <BANLkTimM3dsPxp+oFJuK7JX8iSJRd=BBtA@mail.gmail.com>
On Tue, Apr 12, 2011 at 09:30:42AM +0800, Daniel J Blueman wrote:
> On 11 April 2011 23:45, Josef Bacik <josef@redhat.com> wrote:
> > On 04/11/2011 11:40 AM, Daniel J Blueman wrote:
> >>
> >> Hi Chris,
> >>
> >> This didn't make it in before, so updating to 2.6.39-rc2 and resen=
ding:
> >>
> >> Prevent needless exporting of internal functions from compilation
> >> units by marking them static.
> >>
> >
> > Looks like you have line wrapping on or something, the page looks m=
angled.
> > =A0Thanks,
>=20
> The only way I can solve this in gmail webmail is by attaching the pa=
tch.
>=20
> Is this acceptable? I guess if the mailing list strips patches, I
> guess using both may be a get-out-of-jail...
>
Try using git send-email, that works out well. Thanks,
Josef=20
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2011-04-12 12:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-11 15:40 [PATCH] mark internal functions static Daniel J Blueman
2011-04-11 15:45 ` Josef Bacik
2011-04-12 1:30 ` Daniel J Blueman
2011-04-12 12:41 ` Josef Bacik [this message]
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=20110412124140.GA26337@dhcp231-156.rdu.redhat.com \
--to=josef@redhat.com \
--cc=chris.mason@oracle.com \
--cc=daniel.blueman@gmail.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;
as well as URLs for NNTP newsgroup(s).