From: Chocimier <Chocimier@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: cloud-utils-0.33
Date: Tue, 11 Oct 2022 09:44:00 +0200 [thread overview]
Message-ID: <20221011074400.fBTknPJcN9PIVhLrgn5Xjmpm6p8YphEOUH2PD0onI28@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37968@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1008 bytes --]
New comment by Chocimier on void-packages repository
https://github.com/void-linux/void-packages/pull/37968#issuecomment-1274235102
Comment:
W dniu 13.07.2022 o 20:11, meator pisze:
> Please try to avoid closing and opening the same pull request. The contributing guide <https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#review> shows how to forcefully overwrite your branch when you have issues with your git history. This will work without closing your pull request.
Good point.
> I know Void's commit policy is strange, but there has to be one commit per package. You should never force push to publicly visible repositories unless you have a good reason to do so, but Void doesn't care about that.
One should only avoid altering branches _that others base work on_. PR branches here are not like that, because they are short, single purpose, and others rewrite anyway.
Void-packages master is never rewritten, we push supplemental or `revert` commit if pushed one is wrong.
next prev parent reply other threads:[~2022-10-11 7:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-10 8:43 [PR PATCH] " akhiljalagam
2022-07-10 23:47 ` [PR REVIEW] " classabbyamp
2022-07-11 3:53 ` akhilops
2022-07-11 3:54 ` akhilops
2022-07-11 3:54 ` akhilops
2022-07-11 3:57 ` akhilops
2022-07-11 4:01 ` classabbyamp
2022-07-11 4:02 ` classabbyamp
2022-07-11 4:03 ` classabbyamp
2022-07-13 13:27 ` [PR PATCH] [Updated] " akhiljalagam
2022-07-13 18:11 ` meator
2022-07-14 4:09 ` akhiljalagam
2022-07-14 4:10 ` akhiljalagam
2022-10-11 7:44 ` Chocimier [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-07-09 14:41 [PR PATCH] " akhiljalagam
2022-07-09 15:09 ` Chocimier
2022-07-09 16:32 ` meator
2022-07-10 8:12 ` akhiljalagam
2022-07-10 16:56 ` akhiljalagam
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=20221011074400.fBTknPJcN9PIVhLrgn5Xjmpm6p8YphEOUH2PD0onI28@z \
--to=chocimier@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).