public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Myers <bpm@sgi.com>
To: Thiago Farina <tfransosi@gmail.com>
Cc: Alex Elder <elder@kernel.org>, xfs@oss.sgi.com
Subject: Re: xfs: Remove boolean_t typedef completely.
Date: Tue, 13 Nov 2012 09:24:59 -0600	[thread overview]
Message-ID: <20121113152459.GW31970@sgi.com> (raw)
In-Reply-To: <CACnwZYfVXmy74Fpn0eqa63Zgc89fP9BPoRxXf-=_MhENddjnSw@mail.gmail.com>

Hey Thiago,

On Tue, Nov 13, 2012 at 01:16:43PM -0200, Thiago Farina wrote:
> On Tue, Nov 13, 2012 at 12:32 AM, Ben Myers <bpm@sgi.com> wrote:
> >> >> > Also, can you please place patches in line rather than attaching
> >> >> > them. Attaching them means they cannot be quoted in reply. See
> >> >> > Documentation/SubmittingPatches and Documentation/email-clients.txt
> >> >> > for guidelines.
> None of these docs say anything about send-email.
> 
> >> > It's still attached as a base64 encoded attachment, not as inline
> >> > text....
> >> >
> >> Yep, sorry about that. Is just a text file from $(git format-patch master);
> >
> > If you don't mind another try...
> No, thanks. It's too painful to use git send-email, the patch is
> attached, if you want to take it, then fine, if not then it's fine too
> :)

Ok then, no problem.  I can make an accomodation.  Thanks for the patch!  :)

FYI, there are other options than git send-email that work fine too.  Plenty of
folks are using 'quilt mail' and that is fairly painless.  I suggest you take a
peek at that if you're going to post on a regular basis.

Thanks again,
Ben

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      reply	other threads:[~2012-11-13 15:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-13  0:36 xfs: Remove boolean_t typedef completely Thiago Farina
2012-11-13  1:53 ` Dave Chinner
2012-11-13  2:02   ` Thiago Farina
2012-11-13  2:32     ` Ben Myers
2012-11-13 15:16       ` Thiago Farina
2012-11-13 15:24         ` Ben Myers [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=20121113152459.GW31970@sgi.com \
    --to=bpm@sgi.com \
    --cc=elder@kernel.org \
    --cc=tfransosi@gmail.com \
    --cc=xfs@oss.sgi.com \
    /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