]> Lady’s Gitweb - Gitweb/commit
correct a few doubled-word nits in comments and documentation
authorJim Meyering <redacted>
Wed, 28 Mar 2012 08:45:36 +0000 (10:45 +0200)
committerLady <redacted>
Mon, 6 Apr 2026 04:51:32 +0000 (00:51 -0400)
commit5f41702296a6412c8ad69a57f4771701fdfd4d257cc0dc1dfeea1a505ff2c25c
tree3444039316584fb76b0c96a95c3d0bdafc694b0ffbcb140b1585defbb6ca19d4
parent889d35df0016490309489fd7102059b2bbaba8f6b63857287b4b3468af651f44
correct a few doubled-word nits in comments and documentation

Found by running this command:
$ git ls-files -z|xargs -0 perl -0777 -n \
 -e 'while (/\b(then?|[iao]n|i[fst]|but|f?or|at|and|[dt]o)\s+\1\b/gims)' \
 -e '  {' \
 -e '    $n = ($` =~ tr/\n/\n/ + 1);' \
 -e '    ($v = $&) =~ s/\n/\\n/g;' \
 -e '    print "$ARGV:$n:$v\n";' \
 -e '  }'

Why not just git grep -E ...?
That wouldn't work then the doubled words are separated by a newline.
This is derived from a Makefile syntax-check rule in gnulib's maint.mk:
  http://git.sv.gnu.org/cgit/gnulib.git/tree/top/maint.mk

Signed-off-by: Jim Meyering <redacted>
Signed-off-by: Junio C Hamano <redacted>
static/js/lib/cookies.js
This page took 0.251805 seconds and 4 git commands to generate.