On 10/05/2010 06:00 PM, Paul Eggert wrote:
On 10/05/10 14:00, Eric Blake wrote:
Is that the correct historical name, or should this be worded:
@code{parse_datetime} started life as @code{getdate}, as originally
implemented...
Perhaps that would be better. I don't know what its name was
origi
On 10/05/10 14:00, Eric Blake wrote:
> Is that the correct historical name, or should this be worded:
>
> @code{parse_datetime} started life as @code{getdate}, as originally
> implemented...
Perhaps that would be better. I don't know what its name was
originally, though; somebody would have to c
On 10/05/2010 02:52 PM, Paul Eggert wrote:
+++ b/ChangeLog
@@ -1,5 +1,12 @@
2010-10-05 Paul Eggert
+ parse-datetime: do some more renaming
+ * doc/parse-datetime.texi (Authors of parse_datetime): Call it
+ parse_datetime, not get_date. Mention the renaming.
+ * lib/pa
On 10/05/2010 02:52 PM, Paul Eggert wrote:
-...@code{get_date} was originally implemented by Steven M. Bellovin
+...@code{parse_datetime} was originally implemented by Steven M. Bellovin
Is that the correct historical name, or should this be worded:
@code{parse_datetime} started life as @code{
* doc/parse-datetime.texi (Authors of parse_datetime): Call it
parse_datetime, not get_date. Mention the renaming.
* lib/parse-datetime.y: Call it parse_datetime, not getdate,
in comments.
* m4/bison.m4: Likewise.
---
ChangeLog |7 +++
doc/parse-datetime.texi |5 +++--
