From: q66 <q66@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [WIP] chromium: update to 89.0.4389.72
Date: Wed, 03 Mar 2021 19:42:59 +0100 [thread overview]
Message-ID: <20210303184259.7djXgjuokemt8Pb36rF4fC0KNATagZUrndi0KVCc28M@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29205@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 412 bytes --]
New comment by q66 on void-packages repository
https://github.com/void-linux/void-packages/pull/29205#issuecomment-789967689
Comment:
well I'm not expecting it to be finished, i'm just saying the patches tend to depend on each other, so by making patches later in the sequence apply after removing patches earlier in the sequence is just wasting your time (and may result in bugs being introduced by accident)
next prev parent reply other threads:[~2021-03-03 18:43 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 14:20 [PR PATCH] " pullmoll
2021-03-03 15:15 ` [PR PATCH] [Updated] " pullmoll
2021-03-03 15:40 ` pullmoll
2021-03-03 15:49 ` pullmoll
2021-03-03 16:49 ` pullmoll
2021-03-03 17:00 ` pullmoll
2021-03-03 17:06 ` pullmoll
2021-03-03 17:20 ` pullmoll
2021-03-03 17:20 ` ericonr
2021-03-03 17:21 ` ericonr
2021-03-03 17:23 ` pullmoll
2021-03-03 17:23 ` pullmoll
2021-03-03 17:24 ` pullmoll
2021-03-03 17:25 ` pullmoll
2021-03-03 17:27 ` [PR PATCH] [Updated] " pullmoll
2021-03-03 17:30 ` pullmoll
2021-03-03 18:13 ` pullmoll
2021-03-03 18:13 ` q66
2021-03-03 18:15 ` pullmoll
2021-03-03 18:25 ` [PR PATCH] [Updated] " pullmoll
2021-03-03 18:27 ` pullmoll
2021-03-03 18:30 ` pullmoll
2021-03-03 18:32 ` pullmoll
2021-03-03 18:42 ` q66 [this message]
2021-03-03 19:56 ` [PR PATCH] [Updated] " pullmoll
2021-03-07 12:06 ` pullmoll
2021-03-11 19:11 ` [PR PATCH] [Closed]: " q66
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=20210303184259.7djXgjuokemt8Pb36rF4fC0KNATagZUrndi0KVCc28M@z \
--to=q66@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).