Re: [PATCH 1/1 v2] pager: move pager-specific setup into the build
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Aug 2, 2016, 21:15 UTC
- Message-ID
- <xmqqa8gudg8n.fsf@gitster.mtv.corp.google.com>
- In-Reply-To
- <20160801235651.GA7140@starla>
Eric Wong <e@80x24.org> writes:
Show 26 quoted lines
> So v3 will be MORE=FRX, as less was added: > > commit 98170c0c3ba86eb1cc975e7848d075bf2abc1ed0 > Author: ps <ps@FreeBSD.org> > Date: Mon May 22 10:00:00 2000 +0000 > > bmake glue for less. > > and more was nuked: > > commit cde9059fa3e4dc7e259c3864d7536252a5c580a0 > Author: ps <ps@FreeBSD.org> > Date: Mon May 29 13:31:51 2000 +0000 > > Nuke more from the repository. > > And "git branch -r --contains" on both of those commits says > they showed up in the 5.0 release. However, further > investigation says more was even gone by the 4.1.0 release > > git show origin/release/4.1.0:usr.bin/more # non-existent tree > git show origin/release/4.0.0:usr.bin/more # tree still exists > > But, "git show origin/release/4.0.0:usr.bin/more/option.c" > reveals more from those days wouldn't handle -R anyways, > and hopefully nobody is still running 4.0.0...
OK. And they can always set $MORE on their own to work it around, or we can do a release-dependent tweak when somebody screams.