From owner-freebsd-current Tue Jun 8 18:55: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail2.atl.bellsouth.net (mail2.atl.bellsouth.net [205.152.0.22]) by hub.freebsd.org (Postfix) with ESMTP id 24A2E15B34 for ; Tue, 8 Jun 1999 18:54:58 -0700 (PDT) (envelope-from wghicks@bellsouth.net) Received: from wghicks.bellsouth.net (host-209-214-66-15.atl.bellsouth.net [209.214.66.15]) by mail2.atl.bellsouth.net (8.8.8-spamdog/8.8.5) with ESMTP id VAA07294; Tue, 8 Jun 1999 21:54:44 -0400 (EDT) Received: from wghicks (wghicks@localhost [127.0.0.1]) by wghicks.bellsouth.net (8.9.3/8.9.2) with ESMTP id VAA10697; Tue, 8 Jun 1999 21:57:19 -0400 (EDT) (envelope-from wghicks@wghicks.bellsouth.net) Message-Id: <199906090157.VAA10697@bellsouth.net> To: Brian Feldman Cc: current@FreeBSD.ORG, wghicks@wghicks.bellsouth.net Subject: Re: GNU patch gone stale In-reply-to: Your message of "Tue, 08 Jun 1999 15:20:19 EDT." Date: Tue, 08 Jun 1999 21:57:19 -0400 From: W Gerald Hicks Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Our GNU patch has gone stale in the tree. Anyone want to upgrade it to 2.5? > If not, I'll do it myself eventually. Patch 2.1 which we have now is broken > for certain diffs (recently tried with gimp 1.1.5-1.1.6 diffs), while 2.5 > works fine. The gimp patch situation offers a good example why having contrib'ified things backed by a corresponding port can be a Good Thing. Naturally, using the updated version in ports/devel/patch is an easy workaround until you get contrib updated. (We've encountered this here too) Cheers, Jerry Hicks wghicks@bellsouth.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message