From: Artem Bityutskiy <dedekind@infradead.org>
To: Mitch Davis <mjd-linux-mtd@afork.com>
Cc: linux-mtd@lists.infradead.org, Mike Frysinger <vapier.adi@gmail.com>
Subject: Re: mtd-utils: fec.c uses bcopy()
Date: Wed, 08 Oct 2008 09:08:30 +0300 [thread overview]
Message-ID: <1223446110.8051.92.camel@sauron> (raw)
In-Reply-To: <8956d4ca0810072306t64d28c8apa888ede8c7ccbc33@mail.gmail.com>
On Wed, 2008-10-08 at 17:06 +1100, Mitch Davis wrote:
> Hi Mike,
>
> On Wed, Oct 8, 2008 at 4:07 PM, Mike Frysinger <vapier.adi@gmail.com> wrote:
> > On Wed, Oct 8, 2008 at 00:56, Mitch Davis wrote:
> >> On Wed, Oct 8, 2008 at 1:38 PM, Mike Frysinger wrote:
> >>> use `git diff` to generate a diff instead of posting the entire file
> >>> as an attachment.
> >>
> > sorry, my mistake
> >
> >>> really you should use git to send the patch
> >>
> >> Do you mean a git push?
> >
> > no. use the send-email function. read `man git-send-email` for more info.
>
> - Who is best told about the broken git info links on the MTD git web page?
>
> - This process of submitting stuff with git-send-email is not
> documented on the MTD page, but newbies should use it anyway. Can I
> suggest the howto on the MTD page be updated to avoid people like me
> getting it wrong?
> - On my machine (Fedora 9) git-send-email is part of the git-email
> package, not standard git. Others may benefit from knowing this if
> it's part of that updated page.
MTD web site source may be found at:
git://git.infradead.org/mtd-www.git
Please, feel free to add such a HOWTO and send a patch.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2008-10-08 6:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-08 0:27 mtd-utils: fec.c uses bcopy() Mitch Davis
2008-10-08 1:02 ` Mike Frysinger
2008-10-08 2:36 ` Mitch Davis
2008-10-08 2:38 ` Mike Frysinger
2008-10-08 4:56 ` Mitch Davis
2008-10-08 5:07 ` Mike Frysinger
2008-10-08 6:06 ` Mitch Davis
2008-10-08 6:08 ` Artem Bityutskiy [this message]
2008-10-08 6:23 ` Mike Frysinger
2008-10-08 12:43 ` Josh Boyer
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=1223446110.8051.92.camel@sauron \
--to=dedekind@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mjd-linux-mtd@afork.com \
--cc=vapier.adi@gmail.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