Date: Sat, 27 Oct 2012 20:08:28 -0700 From: hiren panchasara <hiren.panchasara@gmail.com> To: Pedro Giffuni <pfg@freebsd.org> Cc: Chris Rees <crees@freebsd.org>, freebsd-hackers@freebsd.org Subject: Re: Porting patch(1) from NetBSD to FreeBSD (was Re: FreeBSD in Google Code-In 2012? You can help too!) Message-ID: <CALCpEUGMy4fPMpzQDPtqmAo0nZU4-w5cXFRaDif0%2BznG9R5jmQ@mail.gmail.com> In-Reply-To: <508C61C1.8090109@FreeBSD.org> References: <CALCpEUHXkyPgqaypkiatx978jjMbiYtvMZC3nNHNpnRSdLf=PA@mail.gmail.com> <CADLo83-%2Bz6oS%2BeRvU=Sucd-DpJqCPRnMvTBSZM_QfC7Y7VwZ_w@mail.gmail.com> <CALCpEUEH9xiSHVyV=FqEVM3m7V3G%2B_5bNnNJKroY3Dnr-RqTXA@mail.gmail.com> <508C61C1.8090109@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Oct 27, 2012 at 3:35 PM, Pedro Giffuni <pfg@freebsd.org> wrote: > Hello Hiren; > > > > On 10/27/2012 16:48, hiren panchasara wrote: > > + Sean, who has been helping me. > > On Sat, Oct 27, 2012 at 2:31 PM, Chris Rees <crees@freebsd.org> wrote: > >> On 27 October 2012 22:17, hiren panchasara <hiren.panchasara@gmail.com> >> wrote: >> > [removing the CC list] >> > >> > On Wed, Oct 24, 2012 at 3:36 PM, Pedro Giffuni <pfg@freebsd.org> wrote= : >> > >> >> (cc'ing -ports and cutting most of the rest) >> >> >> >> > From: Eitan Adler >> >> .> >> >> >On 24 October 2012 13:24, Fernando Apestegu=C3=ADa wrote: >> >> >> Also related to that, what about writing a section about redports[= 1] >> >> >> in the porter's handbook[2]? >> >> > >> >> >This is a good documentation task... but we need more *coding* tasks >> as >> >> well. >> >> > >> >> >> >> We do need to port and test patch (1) from NetBSD or DragonFly to >> replace >> >> GNU patch, and this shouldn't be difficult. >> >> >> > >> > Hi Pedro / List, >> > >> > I am not part of google summer of code but I've tried to port patch(1) >> from >> > NetBSD into FreeBSD head. I hope that is okay. >> > >> > Patching was trivial and It _seems_ to be working fine. >> > >> > I would appreciate any ideas around how to test the changes and how to >> > proceed further. >> >> Have you a patch :)? You're right, there shouldn't have been many >> changes needed. >> > > Will prepare a patch and post here as soon as I get a chance :-) > > > This is great news Hiren, Thanks! > > > The stress test for this utility is the ports tree but before that we hav= e > to > know what will change. > Thanks Pedro! I will have a lot of questions as I am a newbie here. :-) > > What needs to be done is: > > 1- Compare the options between our old patch and the new BSD patch. > Will do. > 2- Document this in FreeBSD's wiki. > I think this needs to be done when we are done deciding on diffs and how the changes look, right? Also, I do not think I have write access to the wiki. > 3- Prepare a port for testing. > Does this need to be a port? I thought this would live in /src/usr.bin/patch. Also, I believe this will co-exist with current gnu patch(1). Is that a right assumption? Thank you, Hiren > > Unfortunately I will be very busy for more than a month and I can't > help much but I am sure some other committer will love to follow > on this. > > Thanks for taking the initiative, that's what FreeBSD needs! > > Pedro. > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CALCpEUGMy4fPMpzQDPtqmAo0nZU4-w5cXFRaDif0%2BznG9R5jmQ>