Date: Sun, 29 May 2016 15:22:47 -0700 From: Ngie Cooper <yaneurabeya@gmail.com> To: Xin Li <delphij@delphij.net> Cc: Cy Schubert <Cy.Schubert@komquats.com>, Pedro Giffuni <pfg@FreeBSD.org>, d@delphij.net, src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-vendor@freebsd.org Subject: Re: svn commit: r300961 - vendor/one-true-awk/dist Message-ID: <BFDD14D9-1D62-4E92-BA3F-859F84569888@gmail.com> In-Reply-To: <d03ad231-5c8d-dbeb-c0ad-f7fb0b835bb6@delphij.net> References: <201605291817.u4TIHnN7040344@slippy.cwsent.com> <d03ad231-5c8d-dbeb-c0ad-f7fb0b835bb6@delphij.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> On May 29, 2016, at 14:53, Xin Li <delphij@delphij.net> wrote: >=20 > On 5/29/16 11:17, Cy Schubert wrote: > [...] >>> There is no public awk public repository AFAICT, but bwk acknowledged=20= >>> the submission. >>>=20 >>> The change to openresolv was merged to the public repository. >>=20 >> As they've acknowledged the submissions, can you please tag the new=20 >> versions of awk and openresolve with the correct upstream version numbers= ,=20 >> please? >=20 > No, I don't believe tagging is useful here and what Pedro have done is > perfectly fine. >=20 > Importing to vendor branch and merge makes sure that the next import > would have these references, and if upstream decided to e.g. refactor > the code, svn will know what to do instead of presenting conflicts for > the person who do the import to resolve. Agreed. The only thing that might have been better is noting the commit for o= ne-true-awk, but it's tricky because it's not publicized like some other pro= jects (kinda similar to how byacc, libdialog, and ncurses are handled...). Thanks, -Ngie=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BFDD14D9-1D62-4E92-BA3F-859F84569888>