On Mon, Jul 29, 2013 at 9:45 PM, Mike Gilbert <[email protected]> wrote: > On Mon, Jul 29, 2013 at 9:41 PM, Mike Gilbert <[email protected]> wrote: >> On Mon, Jul 29, 2013 at 8:03 PM, Rich Freeman <[email protected]> wrote: >>> Final output is: >>> can't find file to patch at input line 17 >>> (messing with -p doesn't help, which will be obvious from a quick >>> inspection of the file vs the tree) >> >> Try applying the patches with patch -p1. > > I just noticed that you said you messed with patch -p, but somehow I > don't believe you. ;-)
Hmm, the issue might be becoming less hazy. Does the file starting with 0001 in your case apply to the files: setup.py | 2 +- tmdb3/tmdb_api.py | 1 + tmdb3/util.py | 4 ++++ 3 files changed, 6 insertions(+), 1 deletion(-) If not, then I suspect this behavior varies depending on the version of git installed, or perhaps even something else. I'm getting patches that purport to apply to README files and contain lines of code. I suspect there is a bug in the version of git I'm running (1.8.1.5)... Rich
