From: Or Gerlitz <ogerlitz-smomgflXvOZWk0Htik3J/w@public.gmane.org>
To: Bart Van Assche
<bart.vanassche-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Roland Dreier <rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
OpenIB
<general-ZwoEplunGu1OwGhvXhtEPSCwEArCW2h5@public.gmane.org>
Subject: Re: Merge process for OFED patches
Date: Wed, 16 Sep 2009 17:46:37 +0300 [thread overview]
Message-ID: <4AB0FA4D.1020009@voltaire.com> (raw)
In-Reply-To: <e2e108260909160739g3191b5fo80064b5c081ab989-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Bart Van Assche wrote:
> I would like to contact the author of the fourth patch. But unfortunately I could not find any author information in that patch.
yes, non signed and unreviewed patches is a common practice of ofed,
does this create legal issues? maybe that would be the way to stop this?
Or.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-09-16 14:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 12:44 Merge process for OFED patches Bart Van Assche
2009-09-16 13:08 ` [ofa-general] " Bart Van Assche
2009-09-16 14:21 ` Roland Dreier
[not found] ` <ada8wgfezrc.fsf-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
2009-09-16 14:39 ` Bart Van Assche
[not found] ` <e2e108260909160739g3191b5fo80064b5c081ab989-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-09-16 14:46 ` Or Gerlitz [this message]
[not found] ` <4AB0FA4D.1020009-smomgflXvOZWk0Htik3J/w@public.gmane.org>
2009-09-17 10:47 ` Bart Van Assche
2009-09-16 15:05 ` Tung, Chien Tin
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=4AB0FA4D.1020009@voltaire.com \
--to=ogerlitz-smomgflxvozwk0htik3j/w@public.gmane.org \
--cc=bart.vanassche-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=general-ZwoEplunGu1OwGhvXhtEPSCwEArCW2h5@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.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 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.