Date: Fri, 1 Apr 2005 15:16:45 -0500 From: Garance A Drosihn <drosih@rpi.edu> To: Dan Nelson <dnelson@allantgroup.com>, Colin Percival <colin.percival@wadham.ox.ac.uk> Cc: freebsd-arch@freebsd.org Subject: Re: Adding bsdiff to the base system Message-ID: <p0621020fbe735b39c6b3@[128.113.24.47]> In-Reply-To: <20050401152805.GA4564@dan.emsphone.com> References: <424B3AAB.6090200@wadham.ox.ac.uk> <Pine.NEB.3.96L.1050401045710.51321C-100000@fledge.watson.org> <20050401134347.GA6676@Pandora.MHoerich.de> <20050401152805.GA4564@dan.emsphone.com>
next in thread | previous in thread | raw e-mail | index | archive | help
At 9:28 AM -0600 4/1/05, Dan Nelson wrote: >In the last episode (Apr 01), Mario Hoerich said: >> # Robert Watson: >> > On Wed, 30 Mar 2005, Colin Percival wrote: >> > > I'd like to add bsdiff/bspatch into the base system. >> [...] >> > I think this would be a useful addition. >> [...] >> >> Not that it's important, but the names probably aren't the best >> possible choice, as 'bsdiff' seems to suggest 'BSD licensed diff'. >> (See bsdtar.) > >Yes, that's what I assumed this thread was about for the first >couple posts. bdiff/bpatch sound like better names. What's the >'s' stand for? I was also confused by the names at first. How about just 'bindiff' and 'binpatch'? These do sound like useful utilities to add, now that I understand what they are... -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p0621020fbe735b39c6b3>