From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.5 required=3.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6F358C07E9D for ; Mon, 19 Jul 2021 17:06:05 +0000 (UTC) Received: from shelob.surriel.com (shelob.surriel.com [96.67.55.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id D5C2260FDB for ; Mon, 19 Jul 2021 17:06:04 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org D5C2260FDB Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=gmail.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=kernelnewbies-bounces+kernelnewbies=archiver.kernel.org@kernelnewbies.org Received: from localhost ([::1] helo=shelob.surriel.com) by shelob.surriel.com with esmtp (Exim 4.94.2) (envelope-from ) id 1m5WiR-00013S-Gv for kernelnewbies@archiver.kernel.org; Mon, 19 Jul 2021 13:06:03 -0400 Received: from mail-vk1-xa30.google.com ([2607:f8b0:4864:20::a30]) by shelob.surriel.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1m5Wge-0007RN-Nj for kernelnewbies@kernelnewbies.org; Mon, 19 Jul 2021 13:04:12 -0400 Received: by mail-vk1-xa30.google.com with SMTP id d7so3979742vkf.2 for ; Mon, 19 Jul 2021 10:04:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=IvEeenrIudDR9PYP7N503X9l7cSWVH8z2MhvffacPGg=; b=bURvTywFjpUBnygbq5Es83LiFXAIMpTy+PCTel3gYYK2SLaJSZdVh9aM64bWlTEY7D S5LG7UpCMiWB/UNElriQEBUDb6p0y7zuu27Ll1sqBJKQoC7bUktnsNGexduYKuinW6/b UMLiZKbijElyoTK/BtG6u044vwPVBfEDSF/aQ8iJufEIJQeLe4CnYll5qPn/R1rE7MCz CvaNxA5tHzOhaDsMvnEvdGj7umIJ4c0ykUfP6VwLthn4F0CdZZzv910cYqhZQYHdKvQs tNaxF+cStv53PAWGKUicr+AaqwL5X0g9+H253TRw1t+2f3bOuK3x9xAoqDLc0pU63blz 1Ilg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=IvEeenrIudDR9PYP7N503X9l7cSWVH8z2MhvffacPGg=; b=rhDi6rf61Mu+mhA8NkbDGGfJIdhuUALGWVtNLTpCiorXeqUnf+3p2HmhC4i6gStaIg zKpyaNm5rZpIsMdBcQ7lUFdjym+hnUEW5EicdymQNYMrpK0md9BHLF7who/lbwnDJ5Aa STN7H2TlR42LMiIiE26jEV7cvsbk/CtErt0eA1bRHmL6wcSoOmh2g9kp/ujoe9foH2n1 FXQgFXrqYxi3/IZOGgvl7IzrlqOkqqZWzfGRYG9ddrrvhuYlcXruHNynDIi/4S+99L3V VLvHbXO9971mZwtpoCGWebQfU4QZbhrlZb4vyuXK0usYVT1a1iNO4ATlTJsjXTG4Dq2V qDdg== X-Gm-Message-State: AOAM530bJdmwydmhxnAbAkXcOf/jCr9peXLJ+85hiN35yG7hxq++Ckab l0mhkmMLN5lgkPLPCBZr2Lr7w9HH9AhVZYnXT4w= X-Google-Smtp-Source: ABdhPJz/e0vUgRdT/vBA8WOP7v0+5Pc19jxD+V1Yh1iAScqYa6nUW4n/vfrboFPGLSXYuvr8+G8x8oeK4wpuZEchS+0= X-Received: by 2002:a1f:e3c2:: with SMTP id a185mr23183650vkh.3.1626714250547; Mon, 19 Jul 2021 10:04:10 -0700 (PDT) MIME-Version: 1.0 References: <20210704091308.20157-1-abd.masalkhi@gmail.com> <20210712182201.2o6duzdkgspgklby@nitro.local> In-Reply-To: <20210712182201.2o6duzdkgspgklby@nitro.local> From: jim.cromie@gmail.com Date: Mon, 19 Jul 2021 11:03:44 -0600 Message-ID: Subject: Re: How to comment or reply to others? To: Konstantin Ryabitsev Cc: Abd-Alrhman Masalkhi , kernelnewbies X-BeenThere: kernelnewbies@kernelnewbies.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Learn about the Linux kernel List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: kernelnewbies-bounces+kernelnewbies=archiver.kernel.org@kernelnewbies.org > > For example, see this patch for your reference: > https://lore.kernel.org/lkml/20210707055652.962-1-yao.jin@linux.intel.com/ > > If you then require v3 of the patch, just use the same format, copy-paste > previous changelog data and add v3, e.g.: > > --- IIUC, that line is the "snip" that maintainer scripts (or maybe git am ?) use to strip the extra info in the patch from the commit ? > v3: > - Fixed something else > Any wisdom to share on content of 0/N intro messages ? I tend to put all -vN-1 info in 0/N, and not in 1-N/ messages, and usually just -vN-1, -vN-2 I dont think anyone cares about what chunks got moved around while grooming the patchset. (which is not to say I know what Im doing...) 0/N messages dont appear to get into merge commits, or at least not always, perhaps its a sub-tree or maintainer preference. It does leave some ambiguity about where to explain the work; overviews in 0/N that dont get into a merge message leave 1..N/ under-explained. maybe my 0/N overviews just suck. ;-) _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies