From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Kees Cook <keescook@chromium.org>
Cc: tools@linux.kernel.org
Subject: Re: [PATCH 0/5] patchwork-bot: Use worktrees for repos
Date: Mon, 13 Dec 2021 17:30:04 -0500 [thread overview]
Message-ID: <163943460451.66209.15259767684450096453.b4-ty@linuxfoundation.org> (raw)
In-Reply-To: <20211201001126.4106635-1-keescook@chromium.org>
On Tue, 30 Nov 2021 16:11:21 -0800, Kees Cook wrote:
> To use patchwork-bot locally, I wanted to use my existing worktrees for
> various repos. This makes a few small improvements and then adds logic
> to deal with specifying branchs and operating in worktrees.
>
> Thanks!
>
> -Kees
>
> [...]
Applied, thanks!
[1/5] patchwork-bot: Note which actions are part of "housekeeping"
commit: bba5718890cbc3704528c028e104dde197d4c49c
[2/5] patchwork-bot: Create CACHEDIR if it is missing
commit: e2dc648b93b77e45fde736ecbff8d0080fca41ff
[3/5] patchwork-bot: Allow limiting heads to single branch
commit: 36971ee3ad62a56f40c3663a82b7475151df2a77
[4/5] patchwork-bot: Handle repo being a worktree
commit: 460990bdca13805f7e9b5d6c8037437f655bcfac
[5/5] patchwork-bot: Allow initial database to skip recent commits
commit: 6fc2e91a876b0a2771eedb0fe6106d7f47eb8aab
Best regards,
--
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
prev parent reply other threads:[~2021-12-13 22:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 0:11 [PATCH 0/5] patchwork-bot: Use worktrees for repos Kees Cook
2021-12-01 0:11 ` [PATCH 1/5] patchwork-bot: Note which actions are part of "housekeeping" Kees Cook
2021-12-01 0:11 ` [PATCH 2/5] patchwork-bot: Create CACHEDIR if it is missing Kees Cook
2021-12-01 0:11 ` [PATCH 3/5] patchwork-bot: Allow limiting heads to single branch Kees Cook
2021-12-01 0:11 ` [PATCH 4/5] patchwork-bot: Handle repo being a worktree Kees Cook
2021-12-01 0:11 ` [PATCH 5/5] patchwork-bot: Allow initial database to skip recent commits Kees Cook
2021-12-13 22:30 ` Konstantin Ryabitsev [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=163943460451.66209.15259767684450096453.b4-ty@linuxfoundation.org \
--to=konstantin@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=tools@linux.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.
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 NNTP newsgroup(s).