From: meator <meator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: cloud-utils-0.33
Date: Wed, 13 Jul 2022 20:11:41 +0200 [thread overview]
Message-ID: <20220713181141.2FLwfgIpat8q3PwDds1mJWNo4PQV9lL3XLgOP9KNmAc@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: 946 bytes --]
New comment by meator on void-packages repository
https://github.com/void-linux/void-packages/pull/37968#issuecomment-1183530123
Comment:
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.
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. Knowing how to forcefully alter git's history might be useful to you in other cases too (but you should do these things before you `git push` generally). This is called "sausage making" in the git world. I would recommend you to look up `git rebase -i` and baybe `git reset`.
next prev parent reply other threads:[~2022-07-13 18:11 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 [this message]
2022-07-14 4:09 ` akhiljalagam
2022-07-14 4:10 ` akhiljalagam
2022-10-11 7:44 ` Chocimier
-- 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=20220713181141.2FLwfgIpat8q3PwDds1mJWNo4PQV9lL3XLgOP9KNmAc@z \
--to=meator@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).