ntle learning curve.
Cheers,
Jesse Smith
Thank you for the updated manual page. I've applied this change to my tree.
- Jesse
I believe this issue, with patch failing when it cannot open the
non-existent file, has been fixed in my tree [1]. I'm hoping to get it
pushed into the next version.
- Jesse
1. https://github.com/slicer69/patch/tree/54845
Having successfully handed over my copyright claims for Patch to the
FSF, I decided to start by exploring some minor issues that have been
reported by downstream projects, like Debian and FreeBSD. Little
housekeeping tasks where I might be helpful and learn more about the
code & documentation.
In response to Savannah bug report #28453 [1], I am attaching a patch
which allows Patch to print the name of the file it was working on when
an error occurs. Now instead of reporting something like "patch: No
space on disk." We get something more helpful like "patch: Write error
when operating
I took a stab at addressing Savannah bug #44102 [1], which pointed out
Patch will silently change file permissions, even if the original
permissions listed in the diff file do not match the actual permissions
on the disk.
While looking into this issue I discovered a second, related issue. The
As I understand it, in order to become a contributor to GNU Patch, it is
necessary to sign an agreement to assign copyright to either Patch or to
the GNU project.
I'd like to become a member of the GNU Patch team and was wondering what
the process is for signing this agreement so that my patches
>
> Thank you. I'll need you to please fill out the following form and
> send it to ass...@gnu.org:
>
>
> http://git.savannah.gnu.org/cgit/gnulib.git/tree/doc/Copyright/request-assign.future
>
> The FSF will then follow up with you. Once that paperwork is done,
> I'll be able to accept your
