[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-i18n-doc
Subject: Re: Migrating Pology to Python 3
From: Adrian Chaves <adrian () chaves ! io>
Date: 2022-10-08 14:55:19
Message-ID: 9018c57eb39deabbff9deee685a6a201 () chaves ! io
[Download RAW message or body]
If I do:
git fetch # update the origin remote, i.e. what is in the remote Git
repository
git diff origin/master..origin/python3 lang/nn # compare the remote Git
repository branches
I get no output. Is it possible you are on an old commit in either
branch?
On 2022-10-08 16:55, Adrian Chaves wrote:
> Most likely I messed up while trying to clean up the patch, will look
> into it.
>
> On 2022-10-08 14:41, Karl Ove Hufthammer wrote:
> Adrian Chaves skreiv 04.10.2022 12:49:
> So I would like every Pology user to test as soon as possible their
> usual workflows with pology with the python3 branch, and report to me
> any issue. I do expect there to be issues. So send me a command to
> reproduce the issue you get, and I will fix it.
>
> I found some changes in the rules triggered by 'posieve check-rules'.
> But it turned out that this was because the Python 3 branch doesn't
> include some recent changes in the rulesets (not very recent -
> committed in July and August this year). Is this intentional? Example
> of differences:
>
> git diff master..python3 lang/nn
[Attachment #3 (unknown)]
<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" \
/></head><body style='font-size: 10pt; font-family: Verdana,Geneva,sans-serif'> <p>If \
I do:</p> <p>git fetch # update the origin remote, i.e. what is in the remote \
Git repository<br />git diff origin/master..origin/python3 lang/nn # compare \
the remote Git repository branches</p> <p>I get no output. Is it possible you are on \
an old commit in either branch?</p> <p id="reply-intro">On 2022-10-08 16:55, Adrian \
Chaves wrote:</p> <blockquote type="cite" style="padding: 0 0.4em; border-left: \
#1010ff 2px solid; margin: 0"> <div id="replybody1">
<div style="font-size: 10pt; font-family: Verdana,Geneva,sans-serif;">
<p>Most likely I messed up while trying to clean up the patch, will look into it.</p>
<p id="v1reply-intro">On 2022-10-08 14:41, Karl Ove Hufthammer wrote:</p>
<blockquote style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0;">
<div class="v1pre" style="margin: 0; padding: 0; font-family: monospace;"><span \
style="white-space: nowrap;">Adrian Chaves skreiv 04.10.2022 12:49:</span>
<blockquote style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0;"><br \
/>So I would like every Pology user to test as soon as possible their usual workflows \
with pology with the python3 branch, and report to me any issue. I do expect there to \
be issues. So send me a command to reproduce the issue you get, and I will fix it.<br \
/><br /></blockquote> I found some changes in the rules triggered by ‘posieve \
check-rules’. But it turned out that this was because the Python 3 branch \
doesn’t include some recent changes in the rulesets (not very recent – \
committed in July and August this year). Is this intentional? Example of \
differences:<br /><br /><span style="white-space: \
nowrap;"> git diff master..python3 lang/nn</span><br \
/><br /></div> </blockquote>
<p><br /></p>
</div>
</div>
</blockquote>
<p><br /></p>
</body></html>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic