From owner-cvs-ports@FreeBSD.ORG  Fri Feb  3 16:35:37 2012
Return-Path: <owner-cvs-ports@FreeBSD.ORG>
Delivered-To: cvs-ports@freebsd.org
Received: by hub.freebsd.org (Postfix, from userid 1033)
	id 764521065675; Fri,  3 Feb 2012 16:35:37 +0000 (UTC)
Date: Fri, 3 Feb 2012 16:35:37 +0000
From: Alexey Dokuchaev <danfe@FreeBSD.org>
To: Eitan Adler <eadler@freebsd.org>
Message-ID: <20120203163537.GA6473@FreeBSD.org>
References: <201202030851.q138pWbE025501@repoman.freebsd.org>
	<CAF6rxgnoOiiT4KeUf1UA2CziGN2UX_sqrWhqDRvWWAo-tL=mPA@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=koi8-r
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAF6rxgnoOiiT4KeUf1UA2CziGN2UX_sqrWhqDRvWWAo-tL=mPA@mail.gmail.com>
User-Agent: Mutt/1.4.2.1i
Cc: Daniel Eischen <deischen@freebsd.org>, cvs-ports@freebsd.org,
	cvs-all@freebsd.org, ports-committers@freebsd.org
Subject: Re: cvs commit: ports/editors/nedit/files patch-util-misc.c
X-BeenThere: cvs-ports@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: CVS commit messages for the ports tree <cvs-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/cvs-ports>,
	<mailto:cvs-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/cvs-ports>
List-Post: <mailto:cvs-ports@freebsd.org>
List-Help: <mailto:cvs-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/cvs-ports>,
	<mailto:cvs-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Feb 2012 16:35:37 -0000

On Fri, Feb 03, 2012 at 10:55:24AM -0500, Eitan Adler wrote:
> On Fri, Feb 3, 2012 at 3:51 AM, Daniel Eischen <deischen@freebsd.org> wrote:
> > deischen š š2012-02-03 08:51:32 UTC
> >
> > šAdded files:
> > š šeditors/nedit/files špatch-util-misc.c
> > šLog:
> > šAdd a patch file to prevent nedit from crashing on file->open or
> > šfile->save operations.
> 
> Is there a reason this patch has not been committed upstream or is
> this temporary until the next release?

I concur.  While it's very tempting to fix FreeBSD port (especially when
it's maintained by you (not you == Daniel, but in general sense)) we should
always first contact upstream maintainers/vendor and submit a fix and (at
best) ask for review.  In case upstream maintainers are not very responsive,
but fix is critical or trivial enough, it's OK to fix such port directly,
but upstream bug tracker should be filled with detailed bug description and
attached patch.

./danfe