Warner Losh wrote:
> OK. I've resolved all the diffs between the git-tree I had and what made it
> into the tree. the upgrade is now complete, and I've pushed my notion of
> what awk should be to the bsd-ota branch in
> https://github.com/bsdimp/awk.git I'll work on folding them into upstream,
>
On Sun, Jun 2, 2019 at 10:55 AM Warner Losh wrote:
> I'm upgrading the in-tree version of one-true-awk. Normally, this isn't a
> problem, but there's a number of small differences I'm still trying
> to figure out due to our... contorted history. Some of the revisions we had
> in the vendor branch
On Sun, Jun 2, 2019 at 11:06 AM Shawn Webb
wrote:
> On Sun, Jun 02, 2019 at 10:55:41AM -0600, Warner Losh wrote:
> > I'm upgrading the in-tree version of one-true-awk. Normally, this isn't a
> > problem, but there's a number of small differences I'm still trying
> > to figure out due to our... co
On Sun, Jun 02, 2019 at 10:55:41AM -0600, Warner Losh wrote:
> I'm upgrading the in-tree version of one-true-awk. Normally, this isn't a
> problem, but there's a number of small differences I'm still trying
> to figure out due to our... contorted history. Some of the revisions we had
> in the vendo
I'm upgrading the in-tree version of one-true-awk. Normally, this isn't a
problem, but there's a number of small differences I'm still trying
to figure out due to our... contorted history. Some of the revisions we had
in the vendor branch of our repo were accepted as-is, some completely, and
some n
