From: lonwillett <lonwillett@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Seafile update
Date: Sat, 24 Apr 2021 09:22:00 +0200 [thread overview]
Message-ID: <20210424072200.h1kMmzZnlGKixr9glrB5Wp-Zk353zNKjrTt1o0b0TKQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30384@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 762 bytes --]
New comment by lonwillett on void-packages repository
https://github.com/void-linux/void-packages/pull/30384#issuecomment-826049182
Comment:
Re: multiple PRs
I can split this into two or three PRs, but note that the first commit is a dependency of the others. So I am not clear on how to do this.
e.g. The "right" way to do this would be two PRs, both of which include the first commit (libsearpc update). But does this work? Is having the same commit in two PRs going to make something unhappy?
Other approaches will break the CI system, at least temporarily. I could submit the update PR, wait until it is accepted and built, and then submit the new seadrive packages, but it seems rather the long way around...
Can you tell me what I should do?
next prev parent reply other threads:[~2021-04-24 7:22 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-20 12:25 [PR PATCH] " lonwillett
2021-04-20 14:12 ` [PR PATCH] [Updated] " lonwillett
2021-04-23 22:52 ` yopito
2021-04-23 22:56 ` yopito
2021-04-24 7:03 ` lonwillett
2021-04-24 7:22 ` lonwillett [this message]
2021-04-24 14:10 ` yopito
2021-04-24 14:49 ` [PR PATCH] [Updated] " lonwillett
2021-04-24 15:53 ` [PR PATCH] [Updated] seafile-{client-qt,libclient}: update to 8.0.1 lonwillett
2021-04-24 22:09 ` [PR REVIEW] " yopito
2021-04-24 22:09 ` yopito
2021-04-24 22:09 ` yopito
2021-04-24 22:09 ` yopito
2021-04-24 23:52 ` lonwillett
2021-04-24 23:52 ` lonwillett
2021-04-25 0:09 ` [PR PATCH] [Updated] " lonwillett
2021-04-25 9:40 ` [PR REVIEW] " yopito
2021-04-25 10:01 ` yopito
2021-04-25 10:03 ` yopito
2021-04-25 10:25 ` [PR REVIEW] " yopito
2021-04-25 10:28 ` [PR PATCH] [Updated] " lonwillett
2021-04-26 18:13 ` yopito
2021-04-26 19:12 ` ericonr
2021-04-26 19:12 ` [PR PATCH] [Merged]: " ericonr
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=20210424072200.h1kMmzZnlGKixr9glrB5Wp-Zk353zNKjrTt1o0b0TKQ@z \
--to=lonwillett@users.noreply.github.com \
--cc=ml@inbox.vuxu.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).