[1/3] sh/ChangeLog: immediatly to immediately
Commit Message
This is the first of a series of patches to spell immediately
correctly. Since sh only had it in the ChangeLog, I didn't know
if there should be a ChangeLog entry to reflect that.
OK to commit?
---
sim/sh/ChangeLog | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Comments
Hello Joel,
On Thu, Aug 21, 2014 at 08:56:25AM -0500, Joel Sherrill wrote:
> This is the first of a series of patches to spell immediately
> correctly. Since sh only had it in the ChangeLog, I didn't know
> if there should be a ChangeLog entry to reflect that.
>
> OK to commit?
Sorry for the late review.
In the past, we have not required a ChangeLog entry for fixes to
the ChangeLog.
I just pushed your patch...
> ---
> sim/sh/ChangeLog | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/sim/sh/ChangeLog b/sim/sh/ChangeLog
> index d2c331c..08db573 100644
> --- a/sim/sh/ChangeLog
> +++ b/sim/sh/ChangeLog
> @@ -1054,7 +1054,7 @@ Thu Sep 14 19:32:59 1995 Stu Grossman (grossman@cygnus.com)
>
> * gencode.c: Back up PC by 2 for breakpoints.
> * interp.c: Move fp regs beyond pc/pr/etc to avoid confusing GDB,
> - which expect pc to immediatly follow regs[].
> + which expect pc to immediately follow regs[].
>
> Fri Sep 8 14:18:13 1995 Ian Lance Taylor <ian@cygnus.com>
@@ -1054,7 +1054,7 @@ Thu Sep 14 19:32:59 1995 Stu Grossman (grossman@cygnus.com)
* gencode.c: Back up PC by 2 for breakpoints.
* interp.c: Move fp regs beyond pc/pr/etc to avoid confusing GDB,
- which expect pc to immediatly follow regs[].
+ which expect pc to immediately follow regs[].
Fri Sep 8 14:18:13 1995 Ian Lance Taylor <ian@cygnus.com>