-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 24/10/2020 20:52, Charles Campbell wrote: > Charles Campbell wrote: >> James McCoy wrote: >>> On Thu, Oct 22, 2020, 21:39 Charles Campbell >>> <[email protected] <mailto:[email protected]>> wrote: >>> >>> I confess that I'm not a git master. It'd be a help if you >>> could send me a patch instead of a commit which I don't use >>> >>> >>> If you append ".diff" to a pull request URL, you get a diff you >>> can download. For example, >>> https://github.com/vim/vim/pull/7188.diff >>> >>> Cheers, James >>> >>> >> >> Hello: >> >> Unfortunately: >> >> sphinx? https://github.com/vim/vim/pull/7188.diff ksh: >> https://github.com/vim/vim/pull/7188.diff: not found [No such >> file or directory] sphinx? >> https://github.com/vim/vim/pull/7188.patch ksh: >> https://github.com/vim/vim/pull/7188.patch: not found [No such >> file or directory] >> >> Regards, Chip Campbell >> > Well, that was dumb on my part. Here's a new and updated problem: > > git pull https://github.com/vim/vim/pull/7188.diff fatal: Not a > git repository (or any parent up to mount point /home) Stopping at > filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set). > > Again, I want to pull the diff/patch and not have it bother what > I've got. I need to check it over, run it through my test suite, > merge it with the latest netrw (at v171b at the moment).
Charles, that URL gives you a plain diff; download it via $ curl -L https://github.com/vim/vim/pull/7188.diff or simply open the URL in the browser and save the page as a text file. You can also stay within Git, but then would have to set up Vim's GitHub repository as a remote, pull it (Vim's GitHub page has all the details behind the "Clone or download" button), and then you can diff it there, but it would be way more complex, and not so useful, anyway, as you maintain your plugin separately from what gets included by Bram. (So sooner or later you'd still need to produce a diff to move the changes over to your copy.) Like Vim, Git has a steep initial learning curve (I've been there as well); take your time! - -- regards, ingo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJflIlmAAoJEA7ziXlAzQ/vIWwH/Az1SjjjNbVwbp8+W7JE+t2J tmEESsMPId38bO2qBe7jSXKXPZdvn/4twaW8JZuid35XxKVRUpC0RH44XiBYHlKB XKe/3/h8HBPJuqUwPrnh7LiQzM3erkiDt0qo8QEovU3SueG5BGwAzWThcHamxoOn DK2eTtz/f3ED91EU8RuZ5g6BvEYVVpLlSx5JQ42SyuuHi8HS4GoXIwE1CA2C0hUD AMN+XBx8rVOQLKR+1rvfWb0UwgMgh4x7LEwf7Glonp0B3cvusoX05s0cT2xHtcrv c7qCzjNB/99KgbRpsNahmre1JqUZ4b9Dd13ENhB9d9Dvmb6BpF8PzLU71jxqmt4= =smqM -----END PGP SIGNATURE----- -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/a024c195-767b-df85-cbb2-0efcd8f1a92a%40ingo-karkat.de.
