git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Martin Langhoff" <martin.langhoff@gmail.com>
To: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Cc: "Gerald Gutierrez" <ggmlfs@gmail.com>,
	"Matthieu Moy" <Matthieu.Moy@imag.fr>,
	"Junio C Hamano" <gitster@pobox.com>,
	git@vger.kernel.org
Subject: Re: git with custom diff for commits
Date: Wed, 19 Dec 2007 12:52:58 +1300	[thread overview]
Message-ID: <46a038f90712181552i46ecb1aof55c7cdfe0f5c079@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0712182246230.23902@racer.site>

On Dec 19, 2007 11:48 AM, Johannes Schindelin
<Johannes.Schindelin@gmx.de> wrote:
> Yes.  Changes, as in "take this _file_ instead".  Not "edit this file,
> remove those lines, add these here, etc.".

Exactly. GIT is a "content tracker" that doesn't care about any
semantic meaning in your files. Here's the file, git will store it, as
is. No conversions, not fancy interpretations. Strict, safe and fast.
(There's a small exception there for DOS-style newlines, which was
much resisted.)

You can add external machinery that is aware of your content semantics
-- as you've done with calling GNU diff with ignore patterns to decide
whether to commit or not. But when you tell GIT to commit something,
there's no guessing or transformation involved.

A lot of what GIT achieves is based on that founding principle. Remove
it, and we're toast. For starters, the internal machinery is based on
SHA1 digests that change if you flip a single byte. That's what makes
git fast and realiable. It's not merely an end-user thing.

cheers,


m

  reply	other threads:[~2007-12-18 23:53 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-17 22:56 git with custom diff for commits Gerald Gutierrez
2007-12-17 23:01 ` Johannes Schindelin
2007-12-17 23:08   ` Matthieu Moy
2007-12-17 23:11     ` Johannes Schindelin
2007-12-17 23:26       ` Junio C Hamano
2007-12-18  8:57         ` Matthieu Moy
2007-12-18  9:25           ` Junio C Hamano
2007-12-18 20:35             ` Gerald Gutierrez
2007-12-18 20:40               ` Junio C Hamano
2007-12-18 20:48                 ` Gerald Gutierrez
2007-12-18 21:27                   ` Johannes Schindelin
2007-12-18 21:51                     ` Gerald Gutierrez
2007-12-18 22:00                       ` Johannes Schindelin
2007-12-18 21:38                   ` Junio C Hamano
2007-12-18 21:51                   ` Matthieu Moy
2007-12-18 22:27                     ` Gerald Gutierrez
2007-12-18 22:48                       ` Johannes Schindelin
2007-12-18 23:52                         ` Martin Langhoff [this message]
2007-12-19  9:01                         ` Matthieu Moy
2007-12-19 12:09                           ` Johannes Schindelin
2007-12-19 12:13                             ` Matthieu Moy
2007-12-19  9:13                       ` Matthieu Moy
2007-12-18 22:29                     ` Gerald Gutierrez
2007-12-17 23:27       ` Gerald Gutierrez

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=46a038f90712181552i46ecb1aof55c7cdfe0f5c079@mail.gmail.com \
    --to=martin.langhoff@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=Matthieu.Moy@imag.fr \
    --cc=ggmlfs@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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 NNTP newsgroup(s).