Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1604225
| From | Daniel Vetter <daniel.vetter@ffwll.ch> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: linux-next: build failure after merge of the drm tree |
| Date | 2017-03-20 09:10 +0100 |
| Message-ID | <tn0y5-1TW-9@gated-at.bofh.it> (permalink) |
| References | <tmTPY-5kh-9@gated-at.bofh.it> <tn0y5-1TW-7@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Mon, Mar 20, 2017 at 9:03 AM, Daniel Vetter <daniel.vetter@ffwll.ch> wrote: > On Mon, Mar 20, 2017 at 1:51 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote: >> This cherry picking of fixes from new development back to Linus' tree >> can be a real pain when so many other changes happen in the same files. > > One possible fix for this would be if you reuse our rerere cache. The > only reason we don't go insane with all the drm conflicts is that we > completely distributed conflict resolution. Developers push a patch, > script tells them there's a conflict, they resolve it, maintainers > never even notice.We only notice when we double-check the merge > resolution when rerere re-applies it for the real backmerge :-) The > merge order in drm-tip should also match what you have in linux-next, > so you should be able to entirely reuse them. > > Anyway, if you trust us enough to scoop up random git rerere caches > (or at least use them to double-check your own), they're all public: > > git://anongit.freedesktop.org/drm-tip rerere-cache > > Or > > https://cgit.freedesktop.org/drm-tip/tree/rr-cache?h=rerere-cache > > Yes we should probably gc them, but disk space is cheap. And the merge order, in case you want to check that. We can adjust it ofc: https://cgit.freedesktop.org/drm-tip/tree/nightly.conf?h=rerere-cache Cheers, Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
linux-next: build failure after merge of the drm tree Stephen Rothwell <sfr@canb.auug.org.au> - 2017-03-20 02:00 +0100
Re: linux-next: build failure after merge of the drm tree Daniel Vetter <daniel.vetter@ffwll.ch> - 2017-03-20 09:10 +0100
Re: linux-next: build failure after merge of the drm tree Daniel Vetter <daniel.vetter@ffwll.ch> - 2017-03-20 09:10 +0100
csiph-web