title: How to use git to see changes to all files since their initial creation?
body: <p>I'm trying to see what edits I've made since an initial commit.</p>
  
  <p>This happens a lot when I import and control code from a vendor.</p>
  
  <p>So the workflow is like this:</p>
  
  <ol>
  <li><code>git add/commit</code> original</li>
  <li>make edits</li>
  <li><code>git commit</code></li>
  <li>go to 2</li>
  </ol>
  
  <p>I'd like to see a record of all of <em>my</em> changes to the files since they were first created.</p>
  
  <p><code>git log -p -- &lt;file&gt;</code> doesn't quite work because the file's initial creation shows up as one giant additional of all lines.  Like so:</p>
  
  <pre><code>commit 82abdc4cc52d70dcabdec4b987632f226a1e8bc4
  Author: Greg Bell &lt;greg@&gt;
  Date:   Fri Aug 26 07:13:22 2016 +1000
  
      initial import from vendor
  
  diff --git a/vendor/source.h b/vendor/source.h
  new file mode 100644
  index 0000000..baf6d8a
  --- /dev/null
  +++ b/vendor/source.h
  @@ -0,0 +1,221 @@
  +/*
  + * Error codes returned by blah.
  + *
  + * Copyright (C) 1998-2000 blah blah
  + *
  + * This program is free software; you can redistribute it and/or modify
  + * it under the terms of the GNU General Public License as published by
  + * the Free Software Foundation; either version 3 of the License, or
  + * (at your option) any later version.
  + *
  + * This program is distributed in the hope that it will be useful,
  + * but WITHOUT ANY WARRANTY; without even the implied warranty of
  + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
  + * GNU General Public License for more details.
  + *
  + * You should have received a copy of the GNU General Public License along
  + * with this program; if not, visit the http://fsf.org website.
  + */
  
  +#define RERR_OK         0
  +#define RERR_SYNTAX     1       /* syntax or usage error */
  .
  . (all 1250 lines shown)
  .
  </code></pre>
  
  <p>This badly clutters the output when I'm running the log on the entire dir instead of just one file.</p>
  
  <p>There are no branches - perhaps a critical initial mistake, though it would be nasty to have to switch branches based on whether I'm bringing in new files or editing existing ones (then merge, etc.)</p>
  
  <p>What I think makes this hard is that files may come in at any time, so may be added all throughout the git history, so I don't think I can use .. or the various <a href="https://git-scm.com/docs/gitrevisions" rel="nofollow">revision syntaxes</a>.</p>
  
  <p>Seems like a simple use case, but my reading of the documentation for <a href="https://git-scm.com/docs/git-log" rel="nofollow">git-log</a>, and Googling, hasn't yielded anything.</p>