On Thu, 15 May 2003, Linux Kernel Mailing List wrote:
> ChangeSet 1.1063.9.23, 2003/05/14 17:56:37-07:00, [email protected]
>
> Check in new SN2 file from Jes' gettimeoffset() patch.
>
>
> # This patch includes the following deltas:
> # ChangeSet 1.1063.9.22 -> 1.1063.9.23
> # (new) -> 1.1 timer.c
> #
>
> timer.c | 85 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 1 files changed, 85 insertions(+)
>
>
> diff -Nru a/timer.c b/timer.c
> --- /dev/null Wed Dec 31 16:00:00 1969
> +++ b/timer.c Wed Jun 18 09:26:40 2003
^^^^^^^
> @@ -0,0 +1,85 @@
> +/*
> + * linux/arch/ia64/sn/kernel/sn2/timer.c
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Just wondering, did this file really end up where it belongs?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
>>>>> On Wed, 18 Jun 2003 20:04:25 +0200 (MEST), Geert Uytterhoeven <[email protected]> said:
>> diff -Nru a/timer.c b/timer.c
>> --- /dev/null Wed Dec 31 16:00:00 1969
>> +++ b/timer.c Wed Jun 18 09:26:40 2003
Geert> ^^^^^^^
>> @@ -0,0 +1,85 @@
>> +/*
>> + * linux/arch/ia64/sn/kernel/sn2/timer.c
Geert> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Geert> Just wondering, did this file really end up where it belongs?
I think it did, eventually: there was another change to undo the
breakage. What happened is that due to some error, the file ended up
in the wrong place in the ia64 linux tree at some point. I then
deleted the bogus file. Unfortunately, you can't make bk forgive such
sins...
--david