From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Maui
Date: Tue, 05 Apr 2022 16:44:43 +0200 [thread overview]
Message-ID: <20220405144443.ME-BJemXf_bFMdiPURkAVLh6t5qtyM7n8tSopHo4lVk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36524@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 583 bytes --]
New comment by paper42 on void-packages repository
https://github.com/void-linux/void-packages/pull/36524#issuecomment-1088801183
Comment:
> Hi, I already did locally, in order to test the build. I'm just new to git, and mean to soft reset to upstream and do again one commit per package as it's defined in the contributing guidelines.
There is a few ways to do this. This is one, but also it would be painful and not optimal. I would suggest to put your changes to each package to a new commit, then `git rebase -i upstream/master` and squash/fixup commits that should be one.
next prev parent reply other threads:[~2022-04-05 14:44 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 21:18 [PR PATCH] Maui Idesmi
2022-04-04 21:19 ` [PR PATCH] [Updated] Maui Idesmi
2022-04-05 8:49 ` Maui paper42
2022-04-05 8:52 ` [PR REVIEW] Maui paper42
2022-04-05 8:52 ` paper42
2022-04-05 12:05 ` Maui Idesmi
2022-04-05 14:44 ` paper42 [this message]
2022-04-05 16:28 ` [PR PATCH] [Updated] Maui Idesmi
2022-04-05 16:31 ` Idesmi
2022-04-05 16:50 ` Idesmi
2022-04-05 17:14 ` Idesmi
2022-04-05 21:31 ` Idesmi
2022-04-05 21:53 ` Idesmi
2022-04-06 9:16 ` Idesmi
2022-04-06 20:13 ` Idesmi
2022-04-09 14:15 ` Maui Idesmi
2022-04-09 14:30 ` Maui Idesmi
2022-04-24 17:33 ` Maui Idesmi
2022-04-24 17:34 ` [PR PATCH] [Updated] Maui Idesmi
2022-04-24 18:42 ` Idesmi
2022-05-17 20:33 ` Idesmi
2022-05-17 20:47 ` Idesmi
2022-05-17 21:18 ` Idesmi
2022-05-18 9:23 ` Idesmi
2022-05-18 10:14 ` Idesmi
2022-06-30 15:29 ` Idesmi
2022-09-29 2:14 ` Maui github-actions
2022-10-13 2:15 ` [PR PATCH] [Closed]: Maui github-actions
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=20220405144443.ME-BJemXf_bFMdiPURkAVLh6t5qtyM7n8tSopHo4lVk@z \
--to=paper42@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).