Bruce Dubbs wrote:
> At the linuxfromscratch project, we document for users how to build a
> relatively complete Linux system from source code. When we do this we
> consider bash to be one of the most important packages in the system.
>
> https://www.linuxfromscratch.org/lfs/view/stable/
>
> O
積丹尼 Dan Jacobson wrote:
> OK, filed https://github.com/scop/bash-completion/issues/417 .
I think https://github.com/scop/bash-completion/issues/323
is an earlier report of the same core issue. That report
doesn't contain details, just links to older reports from
around the time bash-4.2 was relea
Marty E. Plummer wrote:
> On Wed, May 30, 2018 at 09:15:04AM -0400, Chet Ramey wrote:
>> On 5/29/18 8:25 PM, Marty E. Plummer wrote:
>>
If people are willing to do the conversion between patch formats for their
own purposes, more power to them. I don't see any compelling reason to
c
Chet Ramey wrote:
> On 5/29/18 11:44 PM, Todd Zullinger wrote:
>
>> The main difference is the lack of detail in the git commit
>> message. It would great if the same data found in the
>> bash44-019 patch file was added to the git commit message.
>
> This is certa
Hi,
Marty E. Plummer wrote:
>> If people are willing to do the conversion between patch formats for their
>> own purposes, more power to them. I don't see any compelling reason to
>> change the format I use.
>>
> Could I at least convince you to start doing -p1, if not unified?
Don't we essentia
