git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Anton Mitterer <calestyo@gmail.com>
To: git@vger.kernel.org
Subject: FEAUTRE-REQUEST: upon git difftool, files which cannot be modified (persistently) should be made read only
Date: Thu, 16 Oct 2014 04:45:23 +0200	[thread overview]
Message-ID: <1413427523.4706.40.camel@gmail.com> (raw)

Hi.

Apparently since a while, git difftool has the awseome feature,
that it just symlinks the files to the working copy, if a diff with
that is requested.

e.g. something like:
git difftool -d
will have 
/tmp/git-difftool.TWYTA

created with subdirs

left:
-rw-r--r-- 1 user     user      45k Oct 16 04:33 file

right: 
lrwxrwxrwx 1 calestyo calestyo   52 Oct 16 04:33 file -> /home/user/foo/file

When one edits and saves this in one's favourite difftool,... it
actually gets into the working copy.

But of course saving the left (in this example) has no effect, so it
would be nice if all these files were marked readonly, so that one
already sees in the difftool "changes here are useless".


Cheers,
Chris.

                 reply	other threads:[~2014-10-16  2:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1413427523.4706.40.camel@gmail.com \
    --to=calestyo@gmail.com \
    --cc=git@vger.kernel.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 NNTP newsgroup(s).