all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: 23075@debbugs.gnu.org, nikolay.kudryavtsev@gmail.com
Subject: bug#23075: 24.5; vc-git-command should use coding-system-for-read
Date: Mon, 21 Mar 2016 19:21:51 +0200	[thread overview]
Message-ID: <83oaa7691s.fsf@gnu.org> (raw)
In-Reply-To: <87d1qng4aj.fsf@wanadoo.es> (message from Óscar Fuentes on Mon, 21 Mar 2016 17:54:28 +0100)

> From: Óscar Fuentes <ofv@wanadoo.es>
> Cc: Nikolay Kudryavtsev <nikolay.kudryavtsev@gmail.com>,  23075@debbugs.gnu.org
> Date: Mon, 21 Mar 2016 17:54:28 +0100
> 
> Maybe this is related: on a Kubuntu 15.08 box with a 2 week old emacs
> 25.0.92.2 and git 2.5.0, if I visit etc/HELLO (on a Emacs checkout) and
> do `C-x v l' and then, on the *vc-change-log* buffer, put the cursor on
> the last commit (etc/HELLO: Add Armenian and Mongolian greetings.) and
> press `d', the ensuing *vc-diff* buffer contains mostly garbage.

Thanks, indeed it looks like the same problem.  But I'd still like to
be sure there's nothing else; AFAIR the OP has some non-standard Git
setup wrt encoding stuff.





  reply	other threads:[~2016-03-21 17:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-21 11:22 bug#23075: 24.5; vc-git-command should use coding-system-for-read Nikolay Kudryavtsev
2016-03-21 16:16 ` Eli Zaretskii
2016-03-21 16:54   ` Óscar Fuentes
2016-03-21 17:21     ` Eli Zaretskii [this message]
2016-03-21 17:57     ` Andreas Schwab
2016-03-21 18:05       ` Óscar Fuentes
2016-03-21 18:22         ` Eli Zaretskii
2016-03-21 19:38           ` Óscar Fuentes
2016-04-02 10:02             ` Eli Zaretskii
2016-03-21 18:20       ` Eli Zaretskii
2016-03-21 18:45         ` Nikolay Kudryavtsev
2016-03-21 19:17           ` Eli Zaretskii
2016-03-21 19:35             ` Nikolay Kudryavtsev
2016-04-02  9:58           ` Eli Zaretskii

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83oaa7691s.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=23075@debbugs.gnu.org \
    --cc=nikolay.kudryavtsev@gmail.com \
    --cc=ofv@wanadoo.es \
    /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. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.