git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dario Bertini <berdario@gmail.com>
To: git@vger.kernel.org
Subject: diff weirdness (bug?)
Date: Fri, 14 Feb 2014 20:20:04 +0100	[thread overview]
Message-ID: <52FE6C64.4060700@gmail.com> (raw)

git clone git@github.com:ansible/ansible.git
git revert 3616dffb68badb2b8d56

manually solve the conflict (you can look at the commit here:
https://github.com/ansible/ansible/commit/3616dffb68badb2b8d56ef34391d7aae8de79cd6
)

git diff will output:

dario@macbook ~/P/ansible (devel*+|REVERTING)> git diff
diff --cc lib/ansible/constants.py
index c055ccf,6eac602..0000000
--- a/lib/ansible/constants.py
+++ b/lib/ansible/constants.py
@@@ -84,16 -61,8 +84,12 @@@ active_user   = pwd.getpwuid(os.geteuid

  # Needed so the RPM can call setup.py and have modules land in the
  # correct location. See #1277 for discussion
- if getattr(sys, "real_prefix", None):
-     # in a virtualenv
-     DIST_MODULE_PATH = os.path.join(sys.prefix, 'share/ansible/')
- else:
-     DIST_MODULE_PATH = '/usr/share/ansible/'
+ DIST_MODULE_PATH = os.path.join(sys.prefix, 'share/ansible/')

 +# check all of these extensions when looking for yaml files for things
like
 +# group variables
 +YAML_FILENAME_EXTENSIONS = [ "", ".yml", ".yaml" ]
 +
  # sections in config file
  DEFAULTS='defaults'



now, it weirdly/incorrectly says that we added the YAML-related lines

if we remove these 3 lines, we'll get this diff:

dario@macbook ~/P/ansible (devel*+|REVERTING)> git diff --patience
diff --cc lib/ansible/constants.py
index c055ccf,6eac602..0000000
--- a/lib/ansible/constants.py
+++ b/lib/ansible/constants.py
@@@ -84,16 -61,8 +84,9 @@@ active_user   = pwd.getpwuid(os.geteuid

  # Needed so the RPM can call setup.py and have modules land in the
  # correct location. See #1277 for discussion
- if getattr(sys, "real_prefix", None):
-     # in a virtualenv
-     DIST_MODULE_PATH = os.path.join(sys.prefix, 'share/ansible/')
- else:
-     DIST_MODULE_PATH = '/usr/share/ansible/'
+ DIST_MODULE_PATH = os.path.join(sys.prefix, 'share/ansible/')

- # check all of these extensions when looking for yaml files for things
like
- # group variables
- YAML_FILENAME_EXTENSIONS = [ "", ".yml", ".yaml" ]
 +
  # sections in config file
  DEFAULTS='defaults'


even more weirdly, it'll say that we deleted the yaml-related lines

if we also remove one of the extra blank lines next to the yaml lines we
get an empty diff:

dario@macbook ~/P/ansible (devel*+|REVERTING)> git diff
diff --cc lib/ansible/constants.py
index c055ccf,6eac602..0000000
--- a/lib/ansible/constants.py
+++ b/lib/ansible/constants.py


running `git add .` and then checking with git diff --cached will show
that everything is normal

the output is the same also with
git diff --minimal
or
git diff --patience


-- 
xmpp: berdario@gmail.com
bitmessage: BM-2cTYXfGiSTsnx3righ6aHcJSWe4MV17jDP
gpg fingerprint: 3F8D53518012716C4EEF7DF67B498306B3BF75A0 (used just
for signing commits)

             reply	other threads:[~2014-02-14 19:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-14 19:20 Dario Bertini [this message]
2014-02-14 20:03 ` diff weirdness (bug?) Junio C Hamano
2014-02-16 23:31   ` Dario Bertini
2014-02-17 10:20     ` Thomas Rast
2014-02-18 19:12     ` Junio C Hamano

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=52FE6C64.4060700@gmail.com \
    --to=berdario@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).