Github messages for voidlinux
 help / color / mirror / Atom feed
From: chloris-pale-green <chloris-pale-green@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: hunspell-sl_SI-2020.12.31
Date: Sat, 25 Jun 2022 13:20:51 +0200	[thread overview]
Message-ID: <20220625112051.XAOjBbtrJPF-bzI4IZWGZ9DzJEKgiIT21fFhsxJoLmk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37631@inbox.vuxu.org>

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

New comment by chloris-pale-green on void-packages repository

https://github.com/void-linux/void-packages/pull/37631#issuecomment-1166260966

Comment:
I've reverted the revision to 1 and squashed the three commits since "New package," but had issues when pushing them back to `origin` (Updates were rejected because the tip of your current branch is behind). I've had to merge and ended up with an ugly commit history.

If desired, I can just fork the repo again, make a "clean" package in a single commit, and issue another pull request.

  parent reply	other threads:[~2022-06-25 11:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-21 15:50 [PR PATCH] " chloris-pale-green
2022-06-24 20:22 ` classabbyamp
2022-06-25  9:07 ` [PR PATCH] [Updated] " chloris-pale-green
2022-06-25  9:11 ` chloris-pale-green
2022-06-25 10:08 ` paper42
2022-06-25 11:16 ` [PR PATCH] [Updated] " chloris-pale-green
2022-06-25 11:20 ` chloris-pale-green [this message]
2022-06-25 13:38 ` sgn
2022-06-25 14:03 ` [PR PATCH] [Updated] " chloris-pale-green
2022-06-25 14:05 ` chloris-pale-green
2022-06-26  1:16 ` [PR PATCH] [Merged]: " sgn

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=20220625112051.XAOjBbtrJPF-bzI4IZWGZ9DzJEKgiIT21fFhsxJoLmk@z \
    --to=chloris-pale-green@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).