From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-wr1-f53.google.com (mail-wr1-f53.google.com [209.85.221.53]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 01E0C2F80 for ; Mon, 26 Apr 2021 23:51:03 +0000 (UTC) Received: by mail-wr1-f53.google.com with SMTP id k14so7676589wrv.5 for ; Mon, 26 Apr 2021 16:51:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Zy8lWToUipVMvn0XiQVQIZoTcmvgQu3I7mE833hMYwM=; b=ToCV30oNB2ztVsxGgHjZKgWGYHygxvwZYJztsJgiQVka/AYfXPgtqAsCkbKrXUcYSJ Dbk+uYILcXP0AmrWGpJKW+GOr5w6g3RRb6n3pOWgoz6AdCeDYN3X9nv8wwYOMFoCHmXi zXTzcnWvUYUS761p3724CQJUtEHjzKCcj4/s4= 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=Zy8lWToUipVMvn0XiQVQIZoTcmvgQu3I7mE833hMYwM=; b=ubK+9HG0b9TXpMprYXcscnpeKG2JbeK/kY2HPbNimkX7eoTFk1Kk5g0Q+IBOSc9nba 3jAag0wSw3mH6VF897PsEAKA7cxAa9gupx2y3S1I9/9+H5w4btsjqgIH6JbKxuDfhheE IHZUL3kdI+t/PRaZzn5lIfiBXhNH29v8YptO4CkJ0wYNg4MMmtHD0+F/47sfkfMxJdfg esbvi+Vs/mfGFydr37SRtROCL9wdzGD20foo+IbKzer+TWDuOSeIGF5Bjylnv4ESyVFu 8hgD1Gmavdi8eca5AbgCnYCupMW25Z1xHtCK43E/9NcdO4ho2VN8aHdlbMOlv27Bu2j5 dQ9A== X-Gm-Message-State: AOAM530V0Q8F/QlY2KBtLtBGuSM3G9t1BKJ1S3sfy3FUA8MZEh2QwDyC Udqe8+YyB39vf25YYJYJmfQfAJNzsBsgPjObrdQVAA== X-Google-Smtp-Source: ABdhPJxF32ubQrQ4uMZYbdySNXoobqubGy9cvy/FSDol/Pn1ZTkMzxRMY7W4c++5/sLSKJId0rQ9C+kqf8fEIlSU5dg= X-Received: by 2002:adf:e647:: with SMTP id b7mr25328443wrn.43.1619481062390; Mon, 26 Apr 2021 16:51:02 -0700 (PDT) X-Mailing-List: tools@linux.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 References: <20210422112001.22c64fe9@coco.lan> <20210422092916.556e5e50@gandalf.local.home> <20210423080454.78f4f662@coco.lan> <6c221d801c5a6834168207b5ccadc76ac432c766.camel@perches.com> <20210423091320.4f2381b2@coco.lan> <20210423160310.GD5507@sirena.org.uk> In-Reply-To: From: Simon Glass Date: Tue, 27 Apr 2021 09:50:51 +1000 Message-ID: Subject: Re: Better tools for sending patches (was: Re: [MAINTAINER SUMMIT] Rethinking the acceptance policy for "trivial" patches) To: Leon Romanovsky Cc: Mark Brown , Doug Anderson , Mauro Carvalho Chehab , Joe Perches , Rob Herring , Steven Rostedt , James Bottomley , ksummit@lists.linux.dev, tools@linux.kernel.org Content-Type: text/plain; charset="UTF-8" Hi, The docs are on github also : https://github.com/siemens/u-boot/blob/master/tools/patman/README I find it relatively easy to update each patch with a little change log as I change it. Then I know that when I type 'patman send' it will do the right thing. If people have workflows that would benefit from patman's help, but need it to do an extra thing, I certainly accept patches to the tool. Regards, Simon On Sat, 24 Apr 2021 at 03:12, Leon Romanovsky wrote: > > On Fri, Apr 23, 2021 at 05:03:10PM +0100, Mark Brown wrote: > > On Fri, Apr 23, 2021 at 07:52:30AM -0700, Doug Anderson wrote: > > > > > I know it's nearly impossible to get people to change their workflows, > > > but if you're open to it I definitely suggest giving it a try. Simon > > > Glass (the original author) is also quite receptive to improvements. > > > > I have something broadly similar (much more simplistic and overall less > > capable) which I wrote myself - the things I have that this doesn't have > > are: > > > > - Attesting the outgoing patches with b4. > > - Tagging the published series in git. > > I have something similar too, which actually wrapper over git format-patch > that properly set target (net-next, rdma-next, iproute2, rdma-core, mlx5-next > e.t.c) and changes "To;" based on target. > > Thanks