From: Gabriel Scherer <gabriel.scherer@gmail.com>
To: Thomas Refis <thomas.refis@gmail.com>
Cc: "Daniel Bünzli" <daniel.buenzli@erratique.ch>,
"caml users" <caml-list@inria.fr>
Subject: Re: [Caml-list] Doing compiler patch review with a dedicated mailing-list
Date: Mon, 13 Jan 2014 14:51:52 +0100 [thread overview]
Message-ID: <CAPFanBF-GO1E8GX9DOnur8_1FxznXP1BtQV4mOsa+tZnQiQv5Q@mail.gmail.com> (raw)
In-Reply-To: <CAJ_epFNJT-WVYLYxG+rGcuhFP9n+GBwK_uOBgSQB9uKk20brZw@mail.gmail.com>
> I'd have thought that part was pretty obvious.
The remark was clear, but I am more interested in what Daniel *would
like* to see used. He is quite good at ranting against just about
everything, so I have no indication that he would be merrier with
something else.
On Mon, Jan 13, 2014 at 2:43 PM, Thomas Refis <thomas.refis@gmail.com> wrote:
> 2014/1/13 Gabriel Scherer <gabriel.scherer@gmail.com>:
>> On Mon, Jan 13, 2014 at 12:14 PM, Daniel Bünzli
>> <daniel.buenzli@erratique.ch> wrote:
>>> It's not only easy to browse, it's *great* to browse: all the web-based mailing list archives I interact with are not even able to follow a thread running across two month. I really feel we're in 2014.
>>
>> This is a bit too snarky for me to guess what you want.
>
> I'd have thought that part was pretty obvious. If the discussion
> starts on the 28th of a month, and is continued the next month. The
> "sympa" interface gives you no easy way to follow the thread. You need
> to "select" the second month, and find the thread again.
>
>> I'm already doing a few reviews on mantis, and occasionally uses the
>> github in-patch-commenting interface when people send a link to a
>> github-hosted patch (eg. http://caml.inria.fr/mantis/view.php?id=6274
>> ).
>
> Since we're talking about it: I was a bit confused with that review.
> Although *I* find the github interface nicer than mantis and the "in
> patch comments" really useful, I didn't know whether I should answer
> your comments on github or on mantis, and people on mantis might not
> see the comments you did.
> So I'm not sure that's really a good approach. (But of course that
> particular patch was about ocamldoc, which no one really cares about,
> so I guess that's ok)
>
> Thomas.
next prev parent reply other threads:[~2014-01-13 13:52 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-11 15:23 Adrien Nader
2014-01-11 15:41 ` Simon Cruanes
2014-01-13 9:04 ` Adrien Nader
2014-01-13 9:51 ` François Bobot
2014-01-13 10:27 ` Gabriel Scherer
2014-01-13 11:14 ` Daniel Bünzli
2014-01-13 13:26 ` Gabriel Scherer
2014-01-13 13:43 ` Thomas Refis
2014-01-13 13:51 ` Gabriel Scherer [this message]
2014-01-13 13:57 ` Simon Cruanes
2014-01-13 15:03 ` Török Edwin
2014-01-13 13:58 ` Kakadu
2014-02-17 22:55 ` Richard W.M. Jones
2014-01-13 13:57 ` Daniel Bünzli
2014-01-13 22:30 ` Adrien Nader
2014-01-13 22:39 ` Simon Cruanes
2014-01-13 23:09 ` Adrien Nader
2014-01-14 11:13 ` Gabriel Kerneis
2014-01-14 13:23 ` François Bobot
2014-01-14 13:27 ` Thomas Gazagnaire
2014-01-14 14:06 ` Markus Mottl
2014-01-14 14:12 ` Simon Cruanes
2014-01-14 14:55 ` Amir Chaudhry
2014-01-14 15:09 ` François Bobot
2014-01-14 15:11 ` Anil Madhavapeddy
2014-01-13 16:42 ` Yotam Barnoy
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=CAPFanBF-GO1E8GX9DOnur8_1FxznXP1BtQV4mOsa+tZnQiQv5Q@mail.gmail.com \
--to=gabriel.scherer@gmail.com \
--cc=caml-list@inria.fr \
--cc=daniel.buenzli@erratique.ch \
--cc=thomas.refis@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