caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Török Edwin" <edwin+ml-ocaml@etorok.net>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Doing compiler patch review with a dedicated mailing-list
Date: Mon, 13 Jan 2014 17:03:41 +0200	[thread overview]
Message-ID: <52D4004D.3000106@etorok.net> (raw)
In-Reply-To: <20140113135723.GS11251@emmental.inria.fr>

On 01/13/2014 03:57 PM, Simon Cruanes wrote:
> Le Mon, 13 Jan 2014, Thomas Refis a écrit :
>>
>>> 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)
> 
> I like the github interface, but it's clear that it also comes with
> vendor lock-in.

It is probably a matter of what you're used with, for me - coming from Bugzilla - reporting an issue on Github is more complicated,
and less obvious than on Bugzilla.
For example I don't know how to mark an issue as a 'feature request', or 'enhancement' as there are no severities; and I always
have to be careful of special characters that mess up formatting in the body of the issue, and need to put those in <pre> blocks.

I didn't have any considerable problems reporting bugs on Mantis, in fact its probably easier for me than Github, although
I have to admit that I didn't really try searching for bugs on Mantis or Github, and Github might have an advantage there.

Best regards,
--Edwin

  reply	other threads:[~2014-01-13 15:03 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
2014-01-13 13:57               ` Simon Cruanes
2014-01-13 15:03                 ` Török Edwin [this message]
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=52D4004D.3000106@etorok.net \
    --to=edwin+ml-ocaml@etorok.net \
    --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).