From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 55DAA10A0 for ; Mon, 10 Sep 2018 16:40:30 +0000 (UTC) Received: from mail-io0-f176.google.com (mail-io0-f176.google.com [209.85.223.176]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 0AD8BF1 for ; Mon, 10 Sep 2018 16:40:29 +0000 (UTC) Received: by mail-io0-f176.google.com with SMTP id y12-v6so1143020ioj.13 for ; Mon, 10 Sep 2018 09:40:29 -0700 (PDT) Date: Mon, 10 Sep 2018 12:41:07 -0400 From: Konstantin Ryabitsev To: Daniel Vetter Message-ID: <20180910164107.GA4543@chatter> References: <1536592110.4035.5.camel@HansenPartnership.com> <20180910153806.GR16300@sasha-vm> <20180910154738.GA3712@chatter> <20180910161837.GA4459@chatter> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="UlVJffcvxoiEqYs2" Content-Disposition: inline In-Reply-To: Cc: James Bottomley , ksummit Subject: Re: [Ksummit-discuss] [MAINTAINER SUMMIT] community management/subsystem governance List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , --UlVJffcvxoiEqYs2 Content-Type: text/plain; charset=utf-8; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Sep 10, 2018 at 06:23:52PM +0200, Daniel Vetter wrote: >> Hm... For the purposes of cregit or repository hosting? > >For cregit integration. Tbh I don't even know how the current mailing >lists hosted on freedesktop.org infrastructure are integrated into >cregit. But I assume they are somehow, since that's were all the drm >talk is happening. gitlab will also be hosted on fd.o infrastructure >for us. Cregit only considers LKML and the mainline tree -- at least right now. =20 So, as long as all patches and discussions are cc'd to LKML, they will=20 be within cregit's reach. I'm not sure there are any plans to look at=20 any other lists at this point (I'm only very tangentially involved in=20 cregit's development). Kate Stewart would be the right person to ask=20 this. >> That shouldn't be necessary in the near future. There is work under=20 >> way for >> patchwork to accept message-id based URLs, so using the >> lkml.kernel.org/r/message-id URLs in commit messages should be enough for >> cregit to provide a link to the relevant patchwork thread. We will also >> probably end up integrating lore.kernel.org/patchwork with git in a way = that >> would associate patches with final commit-ids and auto-archive them. It's >> not going to be 100% accurate for various reasons, but will at lest prov= ide >> more hooks for projects like cregit to provide extra details about git >> commits. > >There's at least 4 forks of patchwork :-/ The one we have on fd.o has >been doing this since ages. We added the Link: stuff so you can easily >go from e.g. git log to the patch discussion, without a detour through >google. It's too bad that this hasn't percolated up to ozlabs, because I believe=20 numeric-ID based patch links are actually harmful because they are 100%=20 lossy. -K --UlVJffcvxoiEqYs2 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEABYIAB0WIQR2vl2yUnHhSB5njDW2xBzjVmSZbAUCW5aeowAKCRC2xBzjVmSZ bD5IAQDys1jUcuf9LjAnY2Szcb3LatKxNVtIuboGlI1qvwNJdQD/Ws8bm2Y5FW1M orKPheZ6Vok+jlMdW/dPc+offwpr/gE= =SEjk -----END PGP SIGNATURE----- --UlVJffcvxoiEqYs2--