<div>Hi!</div><div> </div><div><div>> I'll try to manually fix this up. </div></div><div> </div><div>Yes, I see:</div><div> </div><div><div><a href="https://github.com/modula3/cm3/commit/dc84ad581614de7644857e30da5c0668642cbb4a" rel="noopener noreferrer" target="_blank">https://github.com/modula3/cm3/commit/dc84ad581614de7644857e30da5c0668642cbb4a</a></div><div>= = =</div><div><div>Manually insert latest pkginfo.txt from github master.</div></div><div>= = =</div></div><div> </div><div> </div><div><div>Thank!</div></div><div> </div><div> </div><div>Best regards, Victor Miasnikov</div><div> </div><div>03.11.2022, 00:16, "Rodney Bates" <rodney.bates@gmx.com>:</div><blockquote><font face="monospace">Hmm.  It looks like pkginfo.txt, in latest commit </font> <a href="https://github.com/modula3/cm3/commit/94db1cadbe5364bc8bb6410bf811bc92d4c1180f" rel="noopener noreferrer">94db1ca</a> in github master<br />has never come into my local master, despite multiple pulls.<br />Thus both my local branches and github rodney-new don't have<br />it.  I'll try to manually fix this up. <br /><br />  <br /> <div>On 11/2/22 12:06, <a href="mailto:vvm@tut.by" rel="noopener noreferrer">vvm@tut.by</a> wrote:</div><blockquote><div>Hi!</div><div> </div><div> Size of diff -u "pkginfo.txt from rodney-new" pkginfo.txt </div><div>is more 4000 bytes.</div><div> </div><div>Best regards, Victor Miasnikov</div><div>P.S.</div><div> </div><blockquote>> CI is now failing to build with gcc</blockquote><div> </div><div>There is only in master and rodney-new branches.</div><div>It can repair ( and already repaired 2 .. 3 weeks ago) by very simple way.</div><div> </div><div>All binary and half-binaries produce on non-local computers, i.e. Github Actions runner.</div><div> </div><div> </div><div> </div><div>02.11.2022, 19:46, "Rodney Bates" <a href="mailto:rodney.bates@gmx.com" rel="noopener noreferrer"><rodney.bates@gmx.com></a>:</div><blockquote> <div>On 11/2/22 03:14, <a href="mailto:vvm@tut.by" rel="noopener noreferrer" target="_blank">vvm@tut.by</a> wrote:</div><blockquote><div>Hi!</div><div> </div><div> </div><div>( In any key, pkginfo.txt in rodney-new branch is very, very strange on 2022-11-02)</div><div> </div></blockquote><br />In the normal github repositories, pkginfo.txt causes complete<br />recompile of the gcc backend.  This is very slow compared to<br />compiling Modula-3 code.  Most of the time,I make no changes<br />to m3cc, but only to code in Modula-3, which I sometimes recompile<br />very frequently, especially to test front end or runtime<br />system changes, which requires 3 complete recompiles in<br />rapid succession.  So I edit my local pkginfo.txt to not do m3cc,<br />for this reason. <br /><br />But I don't want to push that change up.  I got in a mess<br />forgetting to undo it before committing and pushing, and the<br />history now shows evidence of my convoluted process to<br />clean it up before pushing. <br /> <blockquote><div> </div><div>Are You special do not update master branch?</div><div>                            ^^^^^^^</div><div> </div><div>Instead You update rodney-new branch?</div><div> </div><div>( I.e. there is all good?)</div></blockquote><br />After lots of past grief pushing to master, breaking things,<br />and lots of work to unravel it, I now push to master<br />only *after* pushing to rodney-new and being satisfied<br />with the automatic CI tests done there.  Then I push<br />the (hopefully) identical commit to master.  CI is<br />now failing to build with gcc, so I am not yet satisfied<br />to push to master.<br /> <blockquote><div> </div><div> </div><div>Best regards, Victor Miasnikov</div><div> </div><div> </div><div>31.10.2022, 10:16, <a href="mailto:vvm@tut.by" rel="noopener noreferrer" target="_blank">"vvm@tut.by"</a> <a href="mailto:vvm@tut.by" rel="noopener noreferrer" target="_blank"><vvm@tut.by></a>:</div><blockquote><div>Hi!</div><div> </div><div> </div><div>Are You see p280 test results?</div><div>It is good in half of test environments (?)</div><div> </div><div>Best regards, Victor Miasnikov </div><div> </div><div> </div><div> </div><div>31.10.2022, 10:11, "<a href="mailto:vvm@tut.by" rel="noopener noreferrer" target="_blank">vvm@tut.by</a>" <<a href="mailto:vvm@tut.by" rel="noopener noreferrer" target="_blank">vvm@tut.by</a>>:</div><blockquote><div>Hi!</div><div> </div><div>( again personal)</div><div> </div><div> About:</div><div>pkginfo.txt  </div><div> </div><div>We loss history in "blame view".</div><div> </div><div>"History for cm3 / scripts / pkginfo.txt" looks good</div><div> </div><div>Best regards, Victor Miasnikov</div><div> </div><div>27.10.2022, 20:17, "<a href="mailto:vvm@tut.by" rel="noopener noreferrer" target="_blank">vvm@tut.by</a>" <<a href="mailto:vvm@tut.by" rel="noopener noreferrer" target="_blank">vvm@tut.by</a>>:</div><blockquote>
                <div>Hi!</div>
                <div><br />
                </div>
                <div>( non Github,  but personal message)</div>
                <div><br />
                </div>
                <div>  Are You online at this moment?</div>
                <div>I don't remember Time Zone  </div>
                <div><br />
                </div>
                <div><br />
                </div>
                <div>Variant B</div>
                <div><br />
                </div>
                <div>"What are You doing?"</div>
                <div><br />
                </div>
                <div>As I known, anyone with "write rights" on Github
                  can merge rodney-new branch to master branch.</div>
                <div><br />
                </div>
                <div> Yes? Or no?</div>
                <div>  </div>
                <div>Variant A</div>
                <div><br />
                </div>
                <div>I usual use GUI utility "GIT Kraken", but new
                  version 8.10.1 is "hi experimental".</div>
                <div><br />
                </div>
                <div> May be best avoid use 8.10.X at near next week or
                  month </div>
                <div><br />
                </div>
                <div><br />
                </div>
                <div>Best regards, Victor Miasnikov</div>
                <div><br />
                </div>
                <div><br />
                </div>
                <div><br />
                </div>
                <div>-------- Forward message --------</div>
                <div>27.10.2022, 19:23, "Rodney M. Bates" <<a class="b4cc140a61ad6e2cca0049adf245597656221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext 56221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext" href="mailto:notifications@github.com" target="_blank">notifications@github.com</a>>:</div>
                <div><br />
                </div>
                <div class="84b993f26753ce598214d3b52d1e8b9d650a5c42dd024563e29de83aac743ae9957f5d9ac1a1be5ef5f9cd1a8b6a61549dceebaa46f289547fa55ed6c594e4c1970aaed836fa7e1b4402cc3e877e454fc611af8754f78aa8normalize"><br />
                  <br />
                  On 10/26/22 16:46, peter mckinna wrote:<br />
                  > I didn't see a git pull in your earlier email.<br />
                  > You did the fetch which just gets the commits but
                  not<br />
                  > the pull which puts them into the branch. Was
                  that an oversight?<br />
                  ><br />
                  ><br />
                  <br />
                  No, no oversight.  Per Eric's advice from months ago,<br />
                  for getting my local master updated, I fetch, then<br />
                  rebase.  But in backscrolling, I see a mistake.  I<br />
                  actually did a merge upstream/master instead of a
                  rebase,<br />
                  and that was what refused:<br />
                  <br />
                    :~/proj/m3/git-merge/cm3/master$ git merge
                  upstream/master<br />
                    fatal: Not possible to fast-forward, aborting.<br />
                  <br />
                  Moreover, I remember doing some kind of config on
                  merge,<br />
                  that makes it do fast-forward only, which explains the<br />
                  refusal to do it another way.<br />
                  <br />
                  So I tried again with the rebase.  That refused too,
                  but<br />
                  unlike merge, it told me about one simple change to my<br />
                  local master that explains why fast-forward was
                  impossible.<br />
                  Fixing that, the rebase worked as expected.<br />
                  <br />
                  So thanks for the question, as it made me look in the
                  right<br />
                  place to discover the problem.<br />
                  <br />
                  ><br />
                  > On Thu, 27 Oct 2022 at 03:35, Rodney M. Bates <a class="b4cc140a61ad6e2cca0049adf245597656221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext 56221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext" href="mailto:***@***.***" target="_blank">***@***.***</a>><br />
                  > wrote:<br />
                  ><br />
                  > ><br />
                  > ><br />
                  > > On 10/24/22 17:46, peter mckinna wrote:<br />
                  > > > Your local rodney-new should be in sync
                  with the remote, so just<br />
                  > > > merge into master locally, then push.
                  Are the CI testers making<br />
                  > > > changes to rodney-new?<br />
                  > ><br />
                  > > I don't think so.<br />
                  > ><br />
                  > > I prefer creating a merged (or rebased)
                  local rodney-new and pushing<br />
                  > > it first, to avoid risking introducing
                  breakage in github master.<br />
                  > > But.. regardless of that, before I can
                  create a merge either way,<br />
                  > > I have to get github master to pull down,
                  which is where I am stuck<br />
                  > > right now. This used to work.<br />
                  > ><br />
                  > > > I'm not sure about remote merging.<br />
                  > > ><br />
                  > > > This whole CI thing might need
                  examination. I get they are testing<br />
                  > > > on all architectures but as far as I
                  can tell they are only using the C<br />
                  > > > backend whereas they should be testing
                  other backends as well.<br />
                  > > > Also which branches do they test?<br />
                  > > \<br />
                  > > As of the last time I pushed rodney-new, it
                  provoked tests.<br />
                  > ><br />
                  > > > Surely not all branches. How<br />
                  > > > would one get them to test a particular
                  branch? And while we are at it,<br />
                  > > > I think a bit of judicious pruning of
                  some of those github branches<br />
                  > > would be<br />
                  > > > beneficial.<br />
                  > > ><br />
                  > > > On Tue, 25 Oct 2022 at 08:53, Rodney M.
                  Bates <a class="b4cc140a61ad6e2cca0049adf245597656221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext 56221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext" href="mailto:***@***.***" target="_blank">***@***.***</a>><br />
                  > > > wrote:<br />
                  > > ><br />
                  > > > > I have been using an even more
                  conservative (I think) procedure. I<br />
                  > > alter<br />
                  > > > > local master only from github
                  master. Then merge or rebase into my<br />
                  > > local<br />
                  > > > > branch rodney-new, push that up to
                  github rodney-new, and let the CI<br />
                  > > tests<br />
                  > > > > run on it. If they are good
                  enough, then I push local rodney-new to<br />
                  > > > > github master. But now I can't
                  even do step one.<br />
                  > > > ><br />
                  > > > > On 10/24/22 16:05, peter mckinna
                  wrote:<br />
                  > > > > > Eric may have better
                  solutions but I do the following.<br />
                  > > > > ><br />
                  > > > > > If I have been making minor
                  changes on master make sure you are on<br />
                  > > the<br />
                  > > > > > master branch<br />
                  > > > > > on your local machine.<br />
                  > > > > ><br />
                  > > > > > git checkout master<br />
                  > > > > > git branch (to make sure)<br />
                  > > > > > git fetch<br />
                  > > > > > git pull --rebase origin
                  master (rebase creates commits on your local<br />
                  > > > > > master so your changes are
                  the latest - may provoke conflicts)<br />
                  > > > > > git push origin master (sends
                  your local master to remote)<br />
                  > > > > ><br />
                  > > > > > If I have created a local
                  branch I merge on my local machine first<br />
                  > > then<br />
                  > > > > do<br />
                  > > > > > the push.<br />
                  > > > > ><br />
                  > > > > > git checkout master (make
                  sure you are on master locally)<br />
                  > > > > > git fetch<br />
                  > > > > > git pull --rebase origin
                  master<br />
                  > > > > > git merge other-branch (may
                  have conflicts gti tells you what to do)<br />
                  > > > > > git commit -a ( creates a
                  merge commit)<br />
                  > > > > > git push origin master (or
                  just git push works for me)<br />
                  > > > > ><br />
                  > > > > > now master branch should be
                  the same on local and remote.<br />
                  > > > > ><br />
                  > > > > > git log (verify your commits
                  are in place)<br />
                  > > > > ><br />
                  > > > > ><br />
                  > > > > ><br />
                  > > > > ><br />
                  > > > > > On Tue, 25 Oct 2022 at 07:30,
                  Rodney M. Bates <a class="b4cc140a61ad6e2cca0049adf245597656221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext 56221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext" href="mailto:***@***.***" target="_blank">***@***.***</a>><br />
                  > > > > > wrote:<br />
                  > > > > ><br />
                  > > > > > > PS:<br />
                  > > > > > ><br />
                  > > > > > > 1. I am quite sure this
                  is the way I did this last time, some<br />
                  > > months<br />
                  > > > > ago.<br />
                  > > > > > ><br />
                  > > > > > > 2. I have definitely
                  made no changes to my local master copy since<br />
                  > > > > then.<br />
                  > > > > > ><br />
                  > > > > > > 3. I pushed my
                  rodney-new branch up to github, in case somebody<br />
                  > > has an<br />
                  > > > > > > urgent need for its
                  contents.<br />
                  > > > > > ><br />
                  > > > > > > 4. I added a bunch of
                  cases to e019. All give compile errors, as<br />
                  > > > > expected<br />
                  > > > > > > using my latest
                  compiler, built from rodney-new, but don't crash. A<br />
                  > > > > > > couple give a second,
                  probably extraneous, compile message.<br />
                  > > > > > ><br />
                  > > > > > > On 10/24/22 15:01,
                  Rodney Bates wrote:<br />
                  > > > > > > > OK, excuse my
                  frustration, but once again, I can't seem to<br />
                  > > > > > > > get the most basic
                  things done in git, despite a 300+ page<br />
                  > > > > > > > book, a 400+ page
                  book, and lots of helpful emails from last<br />
                  > > fall.<br />
                  > > > > > > ><br />
                  > > > > > > > All I am trying at
                  this point is to get my local master branch<br />
                  > > > > > > > up to date with the
                  github master branch. I have:<br />
                  > > > > > > ><br />
                  > > > > > > >
                  ~/proj/m3/git-merge/cm3/master$ git remote -v<br />
                  > > > > > > > eric <a class="b4cc140a61ad6e2cca0049adf245597656221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext 56221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext" href="https://github.com/coder5506/cm3.git" target="_blank">https://github.com/coder5506/cm3.git</a>
                  (fetch)<br />
                  > > > > > > > eric <a class="b4cc140a61ad6e2cca0049adf245597656221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext 56221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext" href="https://github.com/coder5506/cm3.git" target="_blank">https://github.com/coder5506/cm3.git</a>
                  (push)<br />
                  > > > > > > > origin
                  /home/rodney/proj/m3/git-devel/cm3 (fetch)<br />
                  > > > > > > > origin
                  /home/rodney/proj/m3/git-devel/cm3 (push)<br />
                  > > > > > > > upstream <a class="b4cc140a61ad6e2cca0049adf245597656221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext 56221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext" href="https://github.com/modula3/cm3.git" target="_blank">https://github.com/modula3/cm3.git</a>
                  (fetch)<br />
                  > > > > > > > upstream <a class="b4cc140a61ad6e2cca0049adf245597656221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext 56221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext" href="https://github.com/modula3/cm3.git" target="_blank">https://github.com/modula3/cm3.git</a>
                  (push)<br />
                  > > > > > > ><br />
                  > > > > > > > and have done git
                  fetch:<br />
                  > > > > > > ><br />
                  > > > > > > >
                  ~/proj/m3/git-merge/cm3/master$ git remote -v<br />
                  > > > > > > > eric <a class="b4cc140a61ad6e2cca0049adf245597656221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext 56221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext" href="https://github.com/coder5506/cm3.git" target="_blank">https://github.com/coder5506/cm3.git</a>
                  (fetch)<br />
                  > > > > > > > eric <a class="b4cc140a61ad6e2cca0049adf245597656221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext 56221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext" href="https://github.com/coder5506/cm3.git" target="_blank">https://github.com/coder5506/cm3.git</a>
                  (push)<br />
                  > > > > > > > origin
                  /home/rodney/proj/m3/git-devel/cm3 (fetch)<br />
                  > > > > > > > origin
                  /home/rodney/proj/m3/git-devel/cm3 (push)<br />
                  > > > > > > > upstream <a class="b4cc140a61ad6e2cca0049adf245597656221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext 56221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext" href="https://github.com/modula3/cm3.git" target="_blank">https://github.com/modula3/cm3.git</a>
                  (fetch)<br />
                  > > > > > > > upstream <a class="b4cc140a61ad6e2cca0049adf245597656221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext 56221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext" href="https://github.com/modula3/cm3.git" target="_blank">https://github.com/modula3/cm3.git</a>
                  (push)<br />
                  > > > > > > > <a class="b4cc140a61ad6e2cca0049adf245597656221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext 56221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext" href="mailto:***@***.***" target="_blank">***@***.***</a>:~/proj/m3/git-merge/cm3/master$
                  git fetch upstream<br />
                  > > > > > > > remote: Enumerating
                  objects: 615, done.<br />
                  > > > > > > > remote: Counting
                  objects: 100% (614/614), done.<br />
                  > > > > > > > remote: Compressing
                  objects: 100% (231/231), done.<br />
                  > > > > > > > remote: Total 615
                  (delta 373), reused 592 (delta 367),<br />
                  > > pack-reused 1<br />
                  > > > > > > > Receiving objects:
                  100% (615/615), 556.76 KiB | 1.66 MiB/s, done.<br />
                  > > > > > > > Resolving deltas:
                  100% (373/373), completed with 27 local<br />
                  > > objects.<br />
                  > > > > > > > From <a class="b4cc140a61ad6e2cca0049adf245597656221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext 56221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext" href="https://github.com/modula3/cm3" target="_blank">https://github.com/modula3/cm3</a><br />
                  > > > > > > >
                  57ee5febdb..65ca3e1248 master -> upstream/master<br />
                  > > > > > > > * [new branch] zcxh
                  -> upstream/zcxh<br />
                  > > > > > > ><br />
                  > > > > > > > apparently
                  successfully. so all the files of master on github<br />
                  > > > > > > > should be copied
                  locally inside my .git, and my "remote"<br />
                  > > > > > > > (confusingly
                  misnamed) named upstream should point to my<br />
                  > > > > > > > local copy of the
                  latest github.master.head.<br />
                  > > > > > > ><br />
                  > > > > > > > But:<br />
                  > > > > > > ><br />
                  > > > > > > >
                  ~/proj/m3/git-merge/cm3/master$ git merge
                  upstream/master<br />
                  > > > > > > > fatal: Not possible
                  to fast-forward, aborting.<br />
                  > > > > > > > <a class="b4cc140a61ad6e2cca0049adf245597656221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext 56221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext" href="mailto:***@***.***" target="_blank">***@***.***</a>:~/proj/m3/git-merge/cm3/master$
                  git merge upstream<br />
                  > > master<br />
                  > > > > > > > merge: upstream -
                  not something we can merge<br />
                  > > > > > > ><br />
                  > > > > > > ><br />
                  > > > > > > > Previously, I
                  remember discovering that some git<br />
                  > > > > > > > commands call for
                  "upstream/master" and others "upstream master"<br />
                  > > to<br />
                  > > > > > > > name a (local copy
                  of) a branch at a remote location, but I don't<br />
                  > > > > find<br />
                  > > > > > > > any reference
                  material telling me which, particularly for git<br />
                  > > merge,<br />
                  > > > > > > > so I tried both.
                  Looks like the slash was the right one, but why<br />
                  > > > > > > > does it refuse and
                  what to do?<br />
                  > > > > > > ><br />
                  > > > > > > ><br />
                  > > > > > > > On 10/18/22 21:17,
                  peter mckinna wrote:<br />
                  > > > > > > >> No worries,<br />
                  > > > > > > >><br />
                  > > > > > > >> I have had
                  merge problems of my own in the past.<br />
                  > > > > > > >> While you are
                  at it, have a look at e020. It compiles but<br />
                  > > crashes.<br />
                  > > > > > > >> The stderr.pgm
                  file suggests it should produce a runtime<br />
                  > > > > > > >> error - invalid
                  cycle in super types.<br />
                  > > > > > > >><br />
                  > > > > > > ><br />
                  > > > > > ><br />
                  > > > > > > —<br />
                  > > > > > > Reply to this email
                  directly, view it on GitHub<br />
                  > > > > > > <<br />
                  > > <a class="b4cc140a61ad6e2cca0049adf245597656221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext 56221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext" href="https://github.com/modula3/cm3/issues/1109#issuecomment-1289576520" target="_blank">https://github.com/modula3/cm3/issues/1109#issuecomment-1289576520</a>>,<br />
                  > > > > or<br />
                  > > > > > > unsubscribe<br />
                  > > > > > > <<br />
                  > > > ><br />
                  > > <a class="b4cc140a61ad6e2cca0049adf245597656221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext 56221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext" href="https://github.com/notifications/unsubscribe-auth/ABALZX34KOPHPTMBMK22FETWE3WXVANCNFSM6AAAAAARHTSKR4" target="_blank">https://github.com/notifications/unsubscribe-auth/ABALZX34KOPHPTMBMK22FETWE3WXVANCNFSM6AAAAAARHTSKR4</a><br />
                  > > > > ><br />
                  > > > > > > .<br />
                  > > > > > > You are receiving this
                  because you authored the thread.Message ID:<br />
                  > > > > > > <a class="b4cc140a61ad6e2cca0049adf245597656221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext 56221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext" href="mailto:***@***.***" target="_blank">***@***.***</a>><br />
                  > > > > > ><br />
                  > > > > ><br />
                  > > > > > —<br />
                  > > > > > Reply to this email directly,
                  view it on GitHub <<br />
                  > > > > <a class="b4cc140a61ad6e2cca0049adf245597656221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext 56221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext" href="https://github.com/modula3/cm3/issues/1109#issuecomment-1289615617" target="_blank">https://github.com/modula3/cm3/issues/1109#issuecomment-1289615617</a>>,<br />
                  > > or<br />
                  > > > > unsubscribe <<br />
                  > > > ><br />
                  > > <a class="b4cc140a61ad6e2cca0049adf245597656221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext 56221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext" href="https://github.com/notifications/unsubscribe-auth/ABSVZNDIIQRY5SENVUIWEODWE32ZFANCNFSM6AAAAAARHTSKR4" target="_blank">https://github.com/notifications/unsubscribe-auth/ABSVZNDIIQRY5SENVUIWEODWE32ZFANCNFSM6AAAAAARHTSKR4</a><br />
                  > > > > >.<br />
                  > > > > > You are receiving this
                  because you commented.Message ID: <a class="b4cc140a61ad6e2cca0049adf245597656221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext 56221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext" href="mailto:***@***.***" target="_blank">***@***.***</a>><br />
                  > > > > ><br />
                  > > > ><br />
                  > > > > —<br />
                  > > > > Reply to this email directly, view
                  it on GitHub<br />
                  > > > > <<a class="b4cc140a61ad6e2cca0049adf245597656221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext 56221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext" href="https://github.com/modula3/cm3/issues/1109#issuecomment-1289664620" target="_blank">https://github.com/modula3/cm3/issues/1109#issuecomment-1289664620</a>>,<br />
                  > > or<br />
                  > > > > unsubscribe<br />
                  > > > > <<br />
                  > > <a class="b4cc140a61ad6e2cca0049adf245597656221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext 56221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext" href="https://github.com/notifications/unsubscribe-auth/ABALZX4HSACTPBLNRB6X2XTWE4AMZANCNFSM6AAAAAARHTSKR4" target="_blank">https://github.com/notifications/unsubscribe-auth/ABALZX4HSACTPBLNRB6X2XTWE4AMZANCNFSM6AAAAAARHTSKR4</a><br />
                  > > ><br />
                  > > > > .<br />
                  > > > > You are receiving this because you
                  authored the thread.Message ID:<br />
                  > > > > <a class="b4cc140a61ad6e2cca0049adf245597656221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext 56221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext" href="mailto:***@***.***" target="_blank">***@***.***</a>><br />
                  > > > ><br />
                  > > ><br />
                  > > > —<br />
                  > > > Reply to this email directly, view it
                  on GitHub <<br />
                  > > <a class="b4cc140a61ad6e2cca0049adf245597656221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext 56221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext" href="https://github.com/modula3/cm3/issues/1109#issuecomment-1289727310" target="_blank">https://github.com/modula3/cm3/issues/1109#issuecomment-1289727310</a>>,
                  or<br />
                  > > unsubscribe <<br />
                  > > <a class="b4cc140a61ad6e2cca0049adf245597656221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext 56221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext" href="https://github.com/notifications/unsubscribe-auth/ABSVZNFFRN2YUCATIPIH2CDWE4GTZANCNFSM6AAAAAARHTSKR4" target="_blank">https://github.com/notifications/unsubscribe-auth/ABSVZNFFRN2YUCATIPIH2CDWE4GTZANCNFSM6AAAAAARHTSKR4</a><br />
                  > > >.<br />
                  > > > You are receiving this because you
                  commented.Message ID: <a class="b4cc140a61ad6e2cca0049adf245597656221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext 56221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext" href="mailto:***@***.***" target="_blank">***@***.***</a>><br />
                  > > ><br />
                  > ><br />
                  > > —<br />
                  > > Reply to this email directly, view it on
                  GitHub<br />
                  > > <<a class="b4cc140a61ad6e2cca0049adf245597656221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext 56221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext" href="https://github.com/modula3/cm3/issues/1109#issuecomment-1292311346" target="_blank">https://github.com/modula3/cm3/issues/1109#issuecomment-1292311346</a>>,
                  or<br />
                  > > unsubscribe<br />
                  > > <<a class="b4cc140a61ad6e2cca0049adf245597656221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext 56221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext" href="https://github.com/notifications/unsubscribe-auth/ABALZX7ZJUSZN5HCHHXBDGTWFFMTVANCNFSM6AAAAAARHTSKR4" target="_blank">https://github.com/notifications/unsubscribe-auth/ABALZX7ZJUSZN5HCHHXBDGTWFFMTVANCNFSM6AAAAAARHTSKR4</a>><br />
                  > > .<br />
                  > > You are receiving this because you authored
                  the thread.Message ID:<br />
                  > > <a class="b4cc140a61ad6e2cca0049adf245597656221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext 56221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext" href="mailto:***@***.***" target="_blank">***@***.***</a>><br />
                  > ><br />
                  ><br />
                  > —<br />
                  > Reply to this email directly, view it on GitHub
                  <<a class="b4cc140a61ad6e2cca0049adf245597656221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext 56221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext" href="https://github.com/modula3/cm3/issues/1109#issuecomment-1292689196" target="_blank">https://github.com/modula3/cm3/issues/1109#issuecomment-1292689196</a>>,
                  or unsubscribe <<a class="b4cc140a61ad6e2cca0049adf245597656221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext 56221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext" href="https://github.com/notifications/unsubscribe-auth/ABSVZNHO42WKQZRYYEJ2KRDWFGRDDANCNFSM6AAAAAARHTSKR4" target="_blank">https://github.com/notifications/unsubscribe-auth/ABSVZNHO42WKQZRYYEJ2KRDWFGRDDANCNFSM6AAAAAARHTSKR4</a>>.<br />
                  > You are receiving this because you
                  commented.Message ID: <a class="b4cc140a61ad6e2cca0049adf245597656221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext 56221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext" href="mailto:***@***.***" target="_blank">***@***.***</a>><br />
                  ><br />
                  <p style="color:#666;font-size:small">—<br />
                    Reply to this email directly, <a href="https://github.com/modula3/cm3/issues/1109#issuecomment-1293776014" target="_blank">view it on
                      GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ALUI7HGJEQ3SVKAUW3GZ56LWFKT6NANCNFSM6AAAAAARHTSKR4" target="_blank">unsubscribe</a>.<br />
                    You are receiving this because you commented.<img height="1" src="https://github.com/notifications/beacon/ALUI7HDE6FYLBRU3LA7CBCLWFKT6NA5CNFSM6AAAAAARHTSKR6WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTSNDV2I4.gif" width="1" /><span style="display:none;font-size:0;height:0;max-height:0;max-width:0;opacity:0;overflow:hidden;visibility:hidden;width:0">Message
                      ID: <modula3/cm3/issues/1109/<a class="b4cc140a61ad6e2cca0049adf245597656221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext 56221ecd4cd88a7e220fd42e552d23b7moz-txt-link-freetext" href="mailto:1293776014@github.com" target="_blank">1293776014@github.com</a>></span></p>
                </div>
                <div><br />
                </div>
                <div>-------- Конец пересылаемого сообщения --------</div>
              </blockquote></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote>