From: Hendrik Boom <hendrik@topoi.pooq.com>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Recent hooks design and general github PR issues
Date: Thu, 21 Jul 2016 09:37:39 -0400 [thread overview]
Message-ID: <20160721133739.GB3613@topoi.pooq.com> (raw)
In-Reply-To: <CAHvkLrNFOZD9uVA4eZkOBybR52XJ2kNGhYKsENTq=QzPdLm_=w@mail.gmail.com>
On Thu, Jul 21, 2016 at 12:38:56PM +0000, Fabrice Le Fessant wrote:
> On Thu, Jul 21, 2016 at 2:09 PM Goswin von Brederlow <goswin-v-b@web.de>
> wrote:
>
> > Many other projects use the rule that PR author != merger.
>
>
> But even more other projects don't use that rule, no ? ;-)
Certainly one-man projects don'e/
-- hendrik
prev parent reply other threads:[~2016-07-21 13:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-19 15:08 Yotam Barnoy
2016-07-19 15:36 ` Fabrice Le Fessant
2016-07-19 16:23 ` Yotam Barnoy
2016-07-19 17:28 ` Fabrice Le Fessant
2016-07-19 20:21 ` Alain Frisch
2016-07-21 12:09 ` Goswin von Brederlow
2016-07-21 12:38 ` Fabrice Le Fessant
2016-07-21 13:37 ` Hendrik Boom [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=20160721133739.GB3613@topoi.pooq.com \
--to=hendrik@topoi.pooq.com \
--cc=caml-list@inria.fr \
/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).