[PATCH 2/2] dim: exclude commits from subordinate trees in pull-request

2018-04-30 Thread Daniel Vetter
For trees which integrate other trees it's a bit much to show all the commits pulled in through those other trees - that should all be summarized already in the merge commit. Instead only show commits done in the local tree, whether that's merges or normal commits. --first-parent achieves that. C

[PATCH 1/2] dim: Add new drm upstreams

2018-04-30 Thread Daniel Vetter
We might want to hold of on pushing this one until it's clearer that drm group maintainership takes off. Cc: Dave Airlie Signed-off-by: Daniel Vetter --- dim | 3 +++ 1 file changed, 3 insertions(+) diff --git a/dim b/dim index 1d78ca275c5d..cf7ad2dae35f 100755 --- a/dim +++ b/dim @@ -1863,10

Re: [PATCH] drm-misc.rst: Document commit rights

2018-04-30 Thread Daniel Vetter
On Thu, Apr 26, 2018 at 04:54:23PM +0200, Lukas Wunner wrote: > On Thu, Apr 26, 2018 at 04:25:57PM +0200, Daniel Vetter wrote: > > This is the exact same text as proposed&merged for igt: > > > > https://patchwork.kernel.org/patch/10339739/ > > > > With one minor change: Both regular contributions

[PATCH] dim: handle parse failures in apply_pull better

2018-04-30 Thread Daniel Vetter
We're relying on get fetch failing and set -e, but that doesn't work if we parse nothing: In that case git fetch just fetches upstream and succeed. Dave stumbled over this by feeding a .mbox with dos linefeeds into dim. v2: Use -z and return 1. Cc: Jani Nikula Cc: Dave Airlie Signed-off-by: Dan

Re: -fixes and ff-only

2018-04-30 Thread Jani Nikula
Late to the party... On Wed, 25 Apr 2018, Sean Paul wrote: > Hey maintainers, > I'm noticing a trend which is unlikely to slow down, so I'd like to get > your input. I send my -fixes (and other) pull requests typically on > Wednesday afternoons (ET) to allow Dave plenty of time to pick them up a

Re: [PATCH] dim: handle parse failures in apply_pull better

2018-04-30 Thread Jani Nikula
On Mon, 30 Apr 2018, Daniel Vetter wrote: > We're relying on get fetch failing and set -e, but that doesn't work > if we parse nothing: In that case git fetch just fetches upstream and > succeed. Dave stumbled over this by feeding a .mbox with dos linefeeds > into dim. > > Cc: Dave Airlie > Signe

Re: [PATCH] dim: handle parse failures in apply_pull better

2018-04-30 Thread Jani Nikula
On Mon, 30 Apr 2018, Daniel Vetter wrote: > We're relying on get fetch failing and set -e, but that doesn't work > if we parse nothing: In that case git fetch just fetches upstream and > succeed. Dave stumbled over this by feeding a .mbox with dos linefeeds > into dim. > > Cc: Dave Airlie > Signe

Re: [PATCH] dim: handle parse failures in apply_pull better

2018-04-30 Thread Lukas Wunner
On Mon, Apr 30, 2018 at 08:29:57AM +0200, Daniel Vetter wrote: > We're relying on get fetch failing and set -e, but that doesn't work > if we parse nothing: In that case git fetch just fetches upstream and > succeed. Dave stumbled over this by feeding a .mbox with dos linefeeds > into dim. How abo

Re: [PATCH] dim: handle parse failures in apply_pull better

2018-04-30 Thread Lukas Wunner
On Mon, Apr 30, 2018 at 09:10:06AM +0200, Daniel Vetter wrote: > On Mon, Apr 30, 2018 at 9:08 AM, Lukas Wunner wrote: > > On Mon, Apr 30, 2018 at 08:29:57AM +0200, Daniel Vetter wrote: > >> We're relying on get fetch failing and set -e, but that doesn't work > >> if we parse nothing: In that case

Re: [PATCH] dim: handle parse failures in apply_pull better

2018-04-30 Thread Daniel Vetter
On Mon, Apr 30, 2018 at 9:08 AM, Lukas Wunner wrote: > On Mon, Apr 30, 2018 at 08:29:57AM +0200, Daniel Vetter wrote: >> We're relying on get fetch failing and set -e, but that doesn't work >> if we parse nothing: In that case git fetch just fetches upstream and >> succeed. Dave stumbled over this