From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: NeilBrown <neilb@suse.de>
Cc: "Paweł Sikora" <pluto@agmk.net>, linux-raid@vger.kernel.org
Subject: Re: ANNOUNCE: mdadm 3.2.4 - A tool for managing Soft RAID under Linux
Date: Tue, 15 May 2012 09:03:21 +0200 [thread overview]
Message-ID: <4FB1FFB9.5090300@redhat.com> (raw)
In-Reply-To: <20120515073219.1275b10a@notabene.brown>
On 05/14/12 23:32, NeilBrown wrote:
> On Mon, 14 May 2012 22:58:58 +0200 Jes Sorensen <Jes.Sorensen@redhat.com>
>> If you post a patch without including a proper commit message and
>> signed-off-by lines, which is standard practice, then that is equivalent
>> to you not having posted a patch in the first place.
>>
>> Don't blame others for not doing the basic work everybody else does when
>> posting patches. It really isn't hard to comply with the standard patch
>> posting rules!
>
> I decided a better approach is just to refresh from upstream:
>
> http://gcc.gnu.org/svn/gcc/branches/cilkplus/include/sha1.h
> http://gcc.gnu.org/svn/gcc/branches/cilkplus/libiberty/sha1.c
>
> have been copied into mdadm with just a tiny change to not include config.h
>
> Seems to work, and probably has the *right* fix.
I would tend to agree with you, if not we can hollor at the gcc guys :)
Cheers,
Jes
next prev parent reply other threads:[~2012-05-15 7:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-12 6:36 ANNOUNCE: mdadm 3.2.4 - A tool for managing Soft RAID under Linux Paweł Sikora
2012-05-14 20:30 ` Jes Sorensen
2012-05-14 20:57 ` Paweł Sikora
2012-05-14 20:58 ` Jes Sorensen
2012-05-14 21:32 ` NeilBrown
2012-05-15 7:03 ` Jes Sorensen [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-05-09 1:29 NeilBrown
2012-05-10 14:59 ` Jes Sorensen
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=4FB1FFB9.5090300@redhat.com \
--to=jes.sorensen@redhat.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=pluto@agmk.net \
/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.