Date: Thu, 27 Oct 2016 08:30:52 +0200 From: Franco Fichtner <franco@lastsummer.de> To: Jochen Neumeister <joneum@bsdproject.de> Cc: "freebsd-ports@freebsd.org" <freebsd-ports@freebsd.org> Subject: Re: make makepatch Message-ID: <A5D1FE78-FB93-4C2C-9751-D9D6FEB096C3@lastsummer.de> In-Reply-To: <61b51cd8-18d2-8f70-77c7-ed7dd92c4a0c@bsdproject.de> References: <730bd5a8-d6c2-7e8f-5240-b7d4b6209884@bsdproject.de> <D00C1F21-1BDF-4372-9197-62C72A8CEE92@lastsummer.de> <6a431a63-7692-a667-5fa2-4de3d55d5189@bsdproject.de> <1FA8BED7-A46D-43B8-AE74-C99229350352@lastsummer.de> <61b51cd8-18d2-8f70-77c7-ed7dd92c4a0c@bsdproject.de>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 27 Oct 2016, at 8:28 AM, Jochen Neumeister <joneum@bsdproject.de> wrote: > > Is this now right, that i can only use the new patch in /files? With > "make clean" i delete the work folder and the old patches. If all the previous patches patch a single file, makepatch will generate the patch for the file, because it doesn't care about the ptch context, just the file. If you want, you can deconstruct the new patch file and push the individual chunks into their old files to silence portlint, but that only works if the patches do not depend on each other. Cheers, Franco
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A5D1FE78-FB93-4C2C-9751-D9D6FEB096C3>