From: Brendan Tildesley <mail@brendan.scot>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: 43504@debbugs.gnu.org
Subject: [bug#43504] [PATCH] gnu: Add scantailor-advanced.
Date: Sat, 26 Sep 2020 06:46:34 +1000 [thread overview]
Message-ID: <62CE0D94-95CB-48C7-A6AE-DC2184E87A0D@brendan.scot> (raw)
In-Reply-To: <87imc2ca4j.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 999 bytes --]
On September 25, 2020 10:29:48 PM GMT+10:00, Mathieu Othacehe <othacehe@gnu.org> wrote:
>
>Hello,
>
>> + (uri (git-reference
>> + (url
>"https://github.com/brendan-t/scantailor-advanced")
>> + (commit commit)))
>
>What's the reason for not using the upstream 1.0.16 release? Is the
>only
>reason the addition of the Korean translation? In that case, it could
>be
>contributed upstream or added as a side patch I guess.
>
>Thanks,
>
>Mathieu
Well I saw the merge request for it and it was ignored, so I just added it manually. Also I wasn't using the latest tag release but the latest commit because the release is 2 years old and there are many fixes and changes afterwards. This is not just the latest release plus the translation but the latest commit plus it, in my own repo. It didn't look like the channel owner was planning to make a release any time soon. Do you think I should just use the latest release then and not worry about it?
[-- Attachment #2: Type: text/html, Size: 1392 bytes --]
next prev parent reply other threads:[~2020-09-25 20:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-19 5:52 [bug#43504] [PATCH] gnu: Add scantailor-advanced Brendan Tildesley
2020-09-25 12:29 ` Mathieu Othacehe
2020-09-25 20:46 ` Brendan Tildesley [this message]
2020-10-01 7:37 ` Mathieu Othacehe
2020-10-01 10:23 ` Brendan Tildesley
2020-10-01 12:23 ` bug#43504: " Mathieu Othacehe
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=62CE0D94-95CB-48C7-A6AE-DC2184E87A0D@brendan.scot \
--to=mail@brendan.scot \
--cc=43504@debbugs.gnu.org \
--cc=othacehe@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).