mingw-cross-env-list
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Mingw-cross-env-list] update on pull request


From: Volker Grabsch
Subject: Re: [Mingw-cross-env-list] update on pull request
Date: Thu, 28 May 2015 22:40:31 +0200
User-agent: Mutt/1.5.23 (2014-03-12)

Hi Rashad,

Sorry for not reviewing your pull request and just providing
"organizational" hints, but:

I believe the biggest issue with your pull request is that it is too
big.  Yes, it is split into multiple commits, and that helps a lot.
But as a single pull request this is still an "all or nothing" thing.
That requires quite a lot of resources on the reviewer's side, as all
commits have to be reviewed at once by a single person before it can
be merged safely.  Timothy volunteered and took that time, which is
really great!  Nevertheless, this makes him the the bottle neck, which
was completely unnecessary and avoidable on your side.

I strongly advice to split this pull request into multiple pull
requests, which means creating a separate branch for each topic.  Each
of these branches should be based on "master", i.e. the branches and
commits should not be based upon each other.  The only exception is if
they really build upon each other.  But even then, try to avoid
putting too much into a single pull request.

Especially in a project like MXE that consists of lots of independent
parts, it is absolutely normal that almost every pull request consist
of just a single, small commit.

That way, others can step in to review some parts.  And even for a
single reviewer it is more motivating and satisfying to finish the
reviews step by step, rather than all at once.  If that had been the
case from the very beginning, I bet most of your commits would have
been merged already, leaving only the really controversial ones to be
discussed.

Again, sorry for just talking and not reviewing anything.  But I think
it is important to talk about the elephant in the room.  It is
unhealthy to build more and more guilty conscience on the reviewers,
when the real problem is not on their side and there's nothing they
can do about it.

I hope this helps you to understand how this unfortunate situation
emerged, and what you can do to push things forward, apart from
pinging the reviewers.  Note that regularily pinging the reviewers is
still a good thing to do, but there's a lot more you can do to help us
incorporating your improvements more quickly.


Regards,
Volker


Rashad M schrieb:
> Could you or anyone else in the team can help to get this merged. It been
> tiring and kind of blocking for me to add new packages
> 
> On Fri, May 15, 2015 at 10:24 AM, Rashad M <address@hidden>
> wrote:
> 
> > Just Ping!. any update?
> >
> > On Mon, May 4, 2015 at 5:10 PM, Rashad M <address@hidden>
> > wrote:
> >
> >> Any news?
> >>
> >> On Thu, Apr 23, 2015 at 10:37 PM, Rashad M <address@hidden>
> >> wrote:
> >>
> >>> No problem.
> >>>
> >>> I will ping back later. Any guesstimate ? :)
> >>>
> >>> On Thu, Apr 23, 2015 at 6:20 AM, Timothy Gu <address@hidden>
> >>> wrote:
> >>>
> >>>> On Mon, Apr 20, 2015 at 11:14:56PM +0200, Rashad M wrote:
> >>>> > Hello Timothy,
> >>>> >
> >>>> > I had updated pull request. It much better now. Hopefully we can
> >>>> close this
> >>>> > time. Sorry for silence on my part.
> >>>> >
> >>>> > https://github.com/mxe/mxe/pull/534
> >>>> >
> >>>> > Would it be ok to check it and let me know
> >>>>
> >>>> I will as soon as I find time, which I unfortunately cannot promise
> >>>> when.
> >>>> Thank you for following up on this nevertheless.
> >>>>
> >>>> Timothy
> >>>>
> >>>
> >>>
> >>>
> >>> --
> >>> Regards,
> >>>    Rashad
> >>>
> >>
> >>
> >>
> >> --
> >> Regards,
> >>    Rashad
> >>
> >
> >
> >
> > --
> > Regards,
> >    Rashad
> >
> 
> 
> 
> -- 
> Regards,
>    Rashad

-- 
Volker Grabsch
---<<(())>>---



reply via email to

[Prev in Thread] Current Thread [Next in Thread]