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 16:27:48 +0300 [thread overview]
Message-ID: <C3ZKR51584GC.D8TQOGKUXNKS@121408> (raw)
In-Reply-To: <87h7ul6kdy.fsf@gnu.org>
On Mon Jul 6, 2020 at 2:52 PM EEST, Mathieu Othacehe wrote:
> 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?
I played a bit with the repo and did what you suggested ("git checkout
-- *.po") and I can't attach the output of "git status" anymore because
it's changed, but it was what you expected: filled with modified .po
files. After running "git checkout -- *.po", magit is fast again. Thanks
a lot!
--
Sergiu
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
2020-07-06 13:27 ` Alexandru-Sergiu Marton [this message]
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=C3ZKR51584GC.D8TQOGKUXNKS@121408 \
--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).