Github messages for voidlinux
 help / color / mirror / Atom feed
From: kawaiiamber <kawaiiamber@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Added template for mold.
Date: Wed, 02 Feb 2022 18:54:11 +0100	[thread overview]
Message-ID: <20220202175411.-2nmf9oZmdlw1QcHjbaAbMpYEgxAAivbhrIfUp2nWoo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35305@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 926 bytes --]

New comment by kawaiiamber on void-packages repository

https://github.com/void-linux/void-packages/pull/35305#issuecomment-1028202026

Comment:
Try to keep only one commit since there's only one package - one commit per package (see [CONTRIBUTING.md](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md)). Since there's 12 commits at the moment, reabse and squash them `git rebase -i HEAD~12` and choose `squash`. Change initial commit message to `New package: mold-1.0.2`, or 1.0.3 if you've updated. After squashing, you'll need to force push. `git push origin master -f` For furutre commits, just ammend them to the currect one. `git commit --ammend; git push origin master -f`. If you plan on contributing more, I would also recommend making a branch on your fork to merge against that's not the master branch. People here would usually call that branch the package name. e..g `git checkout -b mold`.

  parent reply	other threads:[~2022-02-02 17:54 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-30  5:41 [PR PATCH] " basicfunc
2022-02-01  7:33 ` [PR PATCH] [Updated] " basicfunc
2022-02-02  9:19 ` kawaiiamber
2022-02-02  9:23 ` [PR REVIEW] " kawaiiamber
2022-02-02  9:24 ` kawaiiamber
2022-02-02  9:32 ` kawaiiamber
2022-02-02  9:41 ` kawaiiamber
2022-02-02 10:06 ` [PR REVIEW] " kawaiiamber
2022-02-02 13:50 ` basicfunc
2022-02-02 13:51 ` [PR REVIEW] " basicfunc
2022-02-02 13:52 ` basicfunc
2022-02-02 14:00 ` [PR PATCH] [Updated] " basicfunc
2022-02-02 14:01 ` basicfunc
2022-02-02 14:05 ` basicfunc
2022-02-02 16:15 ` basicfunc
2022-02-02 17:20 ` basicfunc
2022-02-02 17:43 ` kawaiiamber
2022-02-02 17:50 ` [PR PATCH] [Updated] " basicfunc
2022-02-02 17:54 ` kawaiiamber [this message]
2022-02-02 17:56 ` kawaiiamber
2022-02-02 19:21 ` kawaiiamber
2022-02-02 19:36 ` [PR PATCH] [Closed]: " basicfunc

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=20220202175411.-2nmf9oZmdlw1QcHjbaAbMpYEgxAAivbhrIfUp2nWoo@z \
    --to=kawaiiamber@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).