From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id C1FE745695; Tue, 23 Jul 2024 14:41:47 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id BC6BC4068A; Tue, 23 Jul 2024 14:41:47 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mails.dpdk.org (Postfix) with ESMTP id 3253D4021D for ; Tue, 23 Jul 2024 14:41:46 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1721738505; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=AHtYarjKdYd/VZfZNdcCuTK9ALKbzpzzqndBWMg/m6g=; b=bnBGmWXp6+javoii+S5C6WflM/2lMGHGuNjco2Vluo1rmuXUNALM7HRLzlEAErMyKCCWJA XRUrU7oG0vRtRImeQ6t5cuZ5Q8K8uQEqIOn1OCKdwZPspbCo0x9ZBQJ8ttnT8WDdmpCpqw NZ1S3SBbiZ+gYnIY2k8u+QsO6cMiFfc= Received: from mx-prod-mc-02.mail-002.prod.us-west-2.aws.redhat.com (ec2-54-186-198-63.us-west-2.compute.amazonaws.com [54.186.198.63]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-93-AskF7tGRM-uyVG3p_zpaWg-1; Tue, 23 Jul 2024 08:41:41 -0400 X-MC-Unique: AskF7tGRM-uyVG3p_zpaWg-1 Received: from mx-prod-int-02.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-02.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.15]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx-prod-mc-02.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 496991955D57; Tue, 23 Jul 2024 12:41:39 +0000 (UTC) Received: from RHTRH0061144 (unknown [10.22.64.138]) by mx-prod-int-02.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 8E4E21955D44; Tue, 23 Jul 2024 12:41:36 +0000 (UTC) From: Aaron Conole To: Patrick Robb Cc: Adam Hassick , Ferruh Yigit , Thomas Monjalon , ci@dpdk.org, David Marchand Subject: Re: Adding Series Dependency to Patchwork In-Reply-To: (Patrick Robb's message of "Mon, 22 Jul 2024 12:28:43 -0400") References: <4881077.GXAFRqVoOG@thomas> <76332523-96ac-407d-b937-c1f8a99808fa@amd.com> Date: Tue, 23 Jul 2024 08:41:34 -0400 Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.0 on 10.30.177.15 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: ci@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK CI discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ci-bounces@dpdk.org Patrick Robb writes: > On Mon, Jul 22, 2024 at 12:15=E2=80=AFPM Adam Hassick wrote: > >> > If we go with the URL option, does is still required to differentiate = as >> > "patch-xxx" or "series-yyy", previously they were different IDs, but >> > with URL can patchwork deduce if it is series or patch? If so this can >> > bring a simplification. >> >> No, you can just paste the URL and the Django URL resolver will figure >> out whether it points at a patch or a series. No need to differentiate >> with the URLs. >> >> That's also true of the message ID option too. There isn't much of a >> point in differentiating patch/series message IDs because series do >> not reliably have an email associated with them. > > Sounds good. I want to highlight again for the ci group that all > dependencies will be series dependencies, regardless of whether > "patch-xxx" or "series-yyy" is used. If a patch message id or url is > submitted, it will be mapped to its series url for the dependency. Thanks for the heads up - it means we will probably need to change things in the robot to make sure we support that format when it gets accepted.