From: Yuri Khan <yuri.v.khan@gmail.com>
To: Thorsten Jolitz <tjolitz@gmail.com>
Cc: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: Re: Magit reports binary files that don't exist
Date: Sat, 23 Aug 2014 12:00:20 +0700 [thread overview]
Message-ID: <CAP_d_8UZXLXaBF3K4qvOxFswYyt-UP24o6eTU9sSe_P6b9v8SQ@mail.gmail.com> (raw)
In-Reply-To: <874mx4b2pe.fsf@gmail.com>
On Sat, Aug 23, 2014 at 5:05 AM, Thorsten Jolitz <tjolitz@gmail.com> wrote:
> I'm only working on the console, so I cannot use the mouse. But I will
> follow your recipe anyway, although it seems likely now that my use of
> literal NUL chars in regexps convinced git that my .el files are binary
> files.
Yes, NULs are certainly a reason to consider a file binary.
In console, the recipe is "git log --patch <filename>". This gives you
all commits that modified <filename>, and how they modified it.
prev parent reply other threads:[~2014-08-23 5:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-22 11:23 Magit reports binary files that don't exist Thorsten Jolitz
2014-08-22 13:43 ` Óscar Fuentes
2014-08-22 14:12 ` Yuri Khan
2014-08-22 14:31 ` Thorsten Jolitz
2014-08-22 14:51 ` Óscar Fuentes
2014-08-22 16:06 ` Thorsten Jolitz
2014-08-22 16:25 ` Thorsten Jolitz
2014-08-22 19:40 ` Nicolas Richard
2014-08-22 22:07 ` Thorsten Jolitz
2014-08-23 12:07 ` Nicolas Richard
2014-08-23 12:26 ` Thorsten Jolitz
2014-08-23 20:38 ` Nicolas Richard
2014-08-23 21:31 ` Thorsten Jolitz
2014-08-22 16:43 ` Yuri Khan
2014-08-22 22:05 ` Thorsten Jolitz
2014-08-23 5:00 ` Yuri Khan [this message]
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAP_d_8UZXLXaBF3K4qvOxFswYyt-UP24o6eTU9sSe_P6b9v8SQ@mail.gmail.com \
--to=yuri.v.khan@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=tjolitz@gmail.com \
/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).