git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Matthias Beyer <mail@beyermatthias.de>
To: git@vger.kernel.org
Subject: git maintainer workflow tools?
Date: Sun, 28 Jul 2019 09:23:18 +0200	[thread overview]
Message-ID: <20190728072318.GO1402@hoshi> (raw)

[-- Attachment #1: Type: text/plain, Size: 1662 bytes --]

Hello git community,

I write this email because after several attempts over several months of
searching the internet for this, I still fail to find a proper documentation
and/or tools for the workflow. So this is my last resort.

So what I am looking for is tools to automate contributor and maintainer
workflow, especially:

1) Repliying to each emailpatch of a set of patches with
   "Reviewed-by: <user@host>" (or other trailers)

   Szenario: I see a patchset on a mailinglist. I apply this patchset to my
   local copy of the repository, review it and test it.
   I want to send "Reviewed-by" and "Tested-by" trailers for each patch.


2) Applying a set of emails as patches, where "Reviewed-by" and other trailers
   from the tree of emails are automatically included in the commit message when
   applying (how do the kernel people do this? By hand? I don't think so, do
   they?)

   Szenario: I receive a patchset for my project. Contributors have started a
   discussion on PATCH 1/3, fixup commits/squash commits were sent to the mail
   thread. After a bit of discussion, "Reviewed-by"/"Acked-by" trailers were
   sent.  I want to apply the patches, and include all trailers in the commit
   message that were sent for the corrosponding patchmail.


Fwiw, I'm using mutt as an email reader, but of course such tools can or even
should be MUA-agnostic, right?

I know about git-interpret-trailers, but I fail to see how to use them to
automate the process.

Maybe you know scripts/tools that are ready and available for accomplishing
these tasks.


-- 
Mit freundlichen Grüßen,
Kind regards,
Matthias Beyer

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2019-07-28  7:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-28  7:23 Matthias Beyer [this message]
2019-07-28 14:19 ` git maintainer workflow tools? Theodore Y. Ts'o

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190728072318.GO1402@hoshi \
    --to=mail@beyermatthias.de \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).