From: Alexandru-Sergiu Marton <brown121407@posteo.ro>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: help-guix@gnu.org
Subject: Re: Git clients struggle with Guix
Date: Mon, 06 Jul 2020 15:56:08 +0300 [thread overview]
Message-ID: <87v9j0re52.fsf@posteo.ro> (raw)
In-Reply-To: <87h7ul6kdy.fsf@gnu.org>
Mathieu Othacehe <othacehe@gnu.org> writes:
> I've experienced this behavior when there are some edited .po
> files. I usually run "git checkout -- *.po" to get rid of them.
> You could maybe share the output of "git status" when you are
> having this issue?
That seems to solve it. I attached the output of "git status"
below anyways. After I ran "git checkout -- *.po" as you
suggested, magit works as expected, no more freezes. Thanks a lot!
--8<---------------cut here---------------start------------->8---
On branch master
Your branch is up to date with 'origin/master'.
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)
modified: po/guix/cs.po
modified: po/guix/da.po
modified: po/guix/de.po
modified: po/guix/eo.po
modified: po/guix/es.po
modified: po/guix/fr.po
modified: po/guix/hu.po
modified: po/guix/pl.po
modified: po/guix/pt_BR.po
modified: po/guix/sr.po
modified: po/guix/sv.po
modified: po/guix/ta.po
modified: po/guix/vi.po
modified: po/guix/zh_CN.po
modified: po/packages/da.po
modified: po/packages/de.po
modified: po/packages/eo.po
modified: po/packages/es.po
modified: po/packages/fr.po
modified: po/packages/hu.po
modified: po/packages/pl.po
modified: po/packages/pt_BR.po
modified: po/packages/sr.po
modified: po/packages/vi.po
modified: po/packages/zh_CN.po
Untracked files:
(use "git add <file>..." to include in what will be committed)
t-guix-graph-8386/
t-home-6781/
t-profile-6433.lock
t-profile-6781
t-profile-6781-0-link
t-profile-6781-1-link
t-profile-6781-2-link
t-profile-6781-3-link
t-profile-6781-4-link
t-profile-6781.lock
t-profile-alt-6781
t-profile-alt-6781-1-link
t-profile-alt-6781.lock
no changes added to commit (use "git add" and/or "git commit -a")
--8<---------------cut here---------------end--------------->8---
--
Alexandru-Sergiu Marton
next prev parent reply other threads:[~2020-07-06 12:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-06 12:19 Git clients struggle with Guix Alexandru-Sergiu Marton
2020-07-06 9:52 ` Mathieu Othacehe
2020-07-06 9:58 ` Pierre Neidhardt
2020-07-06 10:05 ` zimoun
2020-07-06 12:56 ` Alexandru-Sergiu Marton [this message]
2020-07-06 13:27 ` Alexandru-Sergiu Marton
2020-07-06 9:59 ` Michael Rohleder
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=87v9j0re52.fsf@posteo.ro \
--to=brown121407@posteo.ro \
--cc=help-guix@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.
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).