Thanks for fixing that. Although the patch says "[Bug#38223 introduced in grep
3.0]", the original bug report is against grep 2.28 and later. Can I take it
that we tried to fix the bug in 3.0 but the fix was incomplete?
- bug#38223: grep >=2.28 cannot handle -wF correctly un... Paul Eggert
- bug#38223: grep >=2.28 cannot handle -wF correct... Stephane Chazelas
- bug#38223: grep >=2.28 cannot handle -wF correct... NIDE, Naoyuki
- bug#38223: grep >=2.28 cannot handle -wF correctly un... Jim Meyering
- bug#38223: grep >=2.28 cannot handle -wF correct... Jim Meyering
- bug#38223: grep >=2.28 cannot handle -wF cor... Norihiro Tanaka
- bug#38223: grep >=2.28 cannot handle -wF... Jim Meyering
- bug#38223: grep >=2.28 cannot handle... Jim Meyering
- bug#38223: grep >=2.28 cannot h... Norihiro Tanaka
- bug#38223: grep >=2.28 cann... Jim Meyering
- bug#38223: grep >=2.28 cann... Paul Eggert
- bug#38223: grep >=2.28 cann... Jim Meyering
- bug#38223: grep >=2.28 cann... Jim Meyering
- bug#38223: grep >=2.28 cannot h... Jim Meyering