aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorCarlos O'Donell <carlos@redhat.com>2014-08-27 11:53:25 -0400
committerCarlos O'Donell <carlos@redhat.com>2014-08-27 11:54:15 -0400
commit45ef66289acbab17278a73512f9b2a9d8a7ca79d (patch)
treed9b7b920b746b3a31233849293e8efa07314dcf3
parent529bf51595fffbe80023e7d895b671391991bb1b (diff)
downloadglibc-45ef66289acbab17278a73512f9b2a9d8a7ca79d.tar
glibc-45ef66289acbab17278a73512f9b2a9d8a7ca79d.tar.gz
glibc-45ef66289acbab17278a73512f9b2a9d8a7ca79d.tar.bz2
glibc-45ef66289acbab17278a73512f9b2a9d8a7ca79d.zip
NEWS: Typo fix: s/wil /will /g
-rw-r--r--NEWS2
1 files changed, 1 insertions, 1 deletions
diff --git a/NEWS b/NEWS
index 85cb778527..e5cbd3ea5e 100644
--- a/NEWS
+++ b/NEWS
@@ -30,7 +30,7 @@ Version 2.20
2.19. This change is reverted in 2.20. The introduced 2.19 symbol versions
of getcontext, setjmp, _setjmp, __sigsetjmp, longjmp, _longjmp, siglongjmp
are preserved pointing straight to the same implementation as the old ones.
- Given that, new callers wil simply provide a too-big buffer to these
+ Given that, new callers will simply provide a too-big buffer to these
functions. Any applications/libraries out there that embed jmp_buf or
ucontext_t in an ABI-relevant data structure that have already been rebuilt
against 2.19 headers will have to rebuilt again. This is necessary in any