Re: Gerrit submit type (was tests/bugs/gfapi/bug-1447266/bug-1447266.t)

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

 




On Tue, May 16, 2017, at 07:06 AM, Raghavendra Talur wrote:
> > Submit
> > type only comes into play after the decision has already been made to
> > enable/allow submission.
> 
> Not true. I have looked into this last year when I sent out the
> mail[1] asking fast-forward to be the submit type. I am now aware that
> fast-forward is wrong method to use. With cherry pick method gerrit
> does not use the information which it uses to show related changes to
> *enforce* submit order.

What I meant to say was that submit type *should* only come into play
after the decision has been made to enable/allow submission.  I keep
forgetting that the Gerrit developers's attitude toward users is one of
active hostility.  As I said, the tools are there.  The fact that
there's not even an option to use information *already at hand* to help
prevent dependency violations (non-dependent patches would be
unaffected) strikes me as borderline insane.
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-devel



[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux