lmi
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [lmi] Should we update libxml and its kin?


From: Greg Chicares
Subject: Re: [lmi] Should we update libxml and its kin?
Date: Fri, 18 Mar 2022 15:05:32 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.6.0

On 2022-03-18 14:12, Vadim Zeitlin wrote:
> 
>  If you'd like, please include the commit from xanadu/xml-build-refresh
> included in https://github.com/let-me-illustrate/lmi/pull/201
Thanks, I'll do that now.

How do I resolve git-status's complaint below? The last time
I saw something like this, I committed it explicitly, which
IIRC was exactly the wrong thing to do; but last time, again
IIRC, the "untracked" complaint went away when I pushed, yet
I have pushed and it still occurs:

/opt/lmi/src/lmi[0]$git status      
On branch master
Your branch is ahead of 'origin/master' by 1 commit.
  (use "git push" to publish your local commits)

Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
  (commit or discard the untracked or modified content in submodules)
        modified:   third_party/libxml2 (untracked content)

no changes added to commit (use "git add" and/or "git commit -a")


reply via email to

[Prev in Thread] Current Thread [Next in Thread]