From: Sylvain Le Gall <sylvain@le-gall.net>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Project hosting for new OCaml projects
Date: Thu, 6 Mar 2014 11:55:35 +0000 (UTC) [thread overview]
Message-ID: <slrnlhgoi6.dsa.sylvain@le-gall.net> (raw)
In-Reply-To: <554B600BA124496EA06BE4CD03D89A9A@erratique.ch>
On 06-03-2014, Daniel Bünzli <daniel.buenzli@erratique.ch> wrote:
> Le mercredi, 5 mars 2014 à 21:10, Christophe Troestler a écrit :
>> On Wed, 5 Mar 2014 21:00:40 +0100, Daniel Bünzli wrote:
>> >
>> > [...] the pull request mechanism is broken (e.g. it completely
>> > muddies history with useless commits) [...]
>>
>> P.S. You can always merge using the command line¹ which does not have
>> that problem.
>>
>> ¹ The URL is provided in the mail Github send you so you do not even
>> have to go to the Github site.
>
> Yes, that's what I do. But that's not the only thing that is broken about pull requests.
>
> I think the mechanism (each pull request is a branch on which you push
> commits) makes it too easy to get non-logical, incoherent commits.
> There's a pull request, you ask for corrections. The contributor
> instead of correcting, amending its commit and force pushing to the
> branch just adds commits to the branch, which results in a sequence of
> commits that may not make much sense on your main branch (even worse
> it may put your project in an intermediate bad state on certain
> checkouts which is bad for git bisecting). Of course you can always
> ask people to do the right thing, but I think the actual contribution
> process should make you do the right thing.
>
> An example here (not to be mean to this fine individual trying to
> contribute to the opam repository):
>
> https://github.com/ocaml/opam-repository/pull/1756
>
> The second commit will make no sense in the history of the opam-repository.
>
I also find the UI and workflow for reviewing code not very good (better
than nothing though)
Have you tried Gerrit ?
http://gerrithub.io/
N.B. you can also run gerrit on your server.
If you have time to try it and you think it is a better alternative,
just let us know.
Cheers,
Sylvain Le Gall
--
Website: http://sylvain.le-gall.net/
OCaml forge: http://forge.ocamlcore.org
OCaml blogs: http://planet.ocaml.org
next prev parent reply other threads:[~2014-03-06 11:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-05 15:13 David Allsopp
2014-03-05 15:24 ` Simon Cruanes
2014-03-05 15:33 ` Yotam Barnoy
2014-03-05 18:00 ` Hezekiah M. Carty
2014-03-06 1:58 ` Francois Berenger
2014-03-05 20:00 ` Daniel Bünzli
[not found] ` <20140305.211003.1668243541649395876.Christophe.Troestler@umons.ac.be>
2014-03-06 9:48 ` Daniel Bünzli
2014-03-06 11:55 ` Sylvain Le Gall [this message]
2014-03-06 12:05 ` Daniel Bünzli
2014-03-06 0:20 ` Sylvain Le Gall
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=slrnlhgoi6.dsa.sylvain@le-gall.net \
--to=sylvain@le-gall.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).