From: Reece Dunn <msclrhd@googlemail.com>
To: Fabian Zeindl <fabian.zeindl@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: weird rename
Date: Tue, 31 May 2011 20:18:00 +0100 [thread overview]
Message-ID: <BANLkTikuZ-ig0einn+GhMh9EJp4jp2TCxg@mail.gmail.com> (raw)
In-Reply-To: <7760D048-5534-42A2-82D2-D5BB9C75739C@gmail.com>
On 31 May 2011 20:12, Fabian Zeindl <fabian.zeindl@gmail.com> wrote:
> Hi,
>
> i use a GUI for git and discovered that it showed me a rename in a commit where i actually replaced a file.
> So i looked at the commit via git show, and found the following:
>
> Binary files /dev/null and b/lib/swt-3.7M7-win32.jar differ
> diff --git a/lib/swt-3.7M7-win64.jar b/lib/swt-3.7M7-win64.jar
>
> Where is the /dev/null coming from?
/dev/null is used to indicate "does not exist" -- it is a file device
on Unix boxes that emits null characters or consumes output sending it
to oblivion :)!
Comparing /dev/null with A -- A is a new (added) file.
Comparing A with /dev/null -- A is deleted.
HTH,
- Reece
next prev parent reply other threads:[~2011-05-31 19:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-31 19:12 weird rename Fabian Zeindl
2011-05-31 19:18 ` Reece Dunn [this message]
2011-05-31 19:19 ` Fabian Zeindl
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=BANLkTikuZ-ig0einn+GhMh9EJp4jp2TCxg@mail.gmail.com \
--to=msclrhd@googlemail.com \
--cc=fabian.zeindl@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).