FYI, small patch required to resync git from cvs

FYI, small patch required to resync git from cvs

[Jim Meyering]

This missing change started showing up in nag email (from my automatic
cvs-git-comparator) recently, so I've just applied it manually,
with Doug listed as author.
It should propagate to the public git repo within the hour.

commit 1b12f5d581827abdf5865c314a58cf3a7874d52e
Author: Doug Evans <dje@sebabeach.org>
Date:   Sun Oct 25 14:57:27 2009 +0000

    cpu: move cgen-types.h and cgen-ops.h into cgen/

    [committed manually by Jim Meyering, in order
     to resync the git mirror from cvs. ]

diff --git a/cpu/ChangeLog b/cpu/ChangeLog
index 2b8c45a..432540f 100644
--- a/cpu/ChangeLog
+++ b/cpu/ChangeLog
@@ -1,3 +1,8 @@
+2009-10-23  Doug Evans  <dje@sebabeach.org>
+
+	* m32c.opc (opc.h): cgen-types.h -> cgen/basic-modes.h.
+	cgen-ops.h -> cgen/basic-ops.h.
+
 2009-09-25  Alan Modra  <amodra@bigpond.net.au>

 	* m32r.cpu (stb-plus): Typo fix.
diff --git a/cpu/m32c.opc b/cpu/m32c.opc
index 40c3075..bc983ea 100644
--- a/cpu/m32c.opc
+++ b/cpu/m32c.opc
@@ -40,8 +40,8 @@
 /* -- opc.h */

 /* Needed for RTL's 'ext' and 'trunc' operators.  */
-#include "cgen-types.h"
-#include "cgen-ops.h"
+#include "cgen/basic-modes.h"
+#include "cgen/basic-ops.h"

 /* We can't use the default hash size because many bits are used by
    operands.  */

git update delay [Re: FYI, small patch required to resync git from cvs]

[Jan Kratochvil]

On Sun, 25 Oct 2009 16:02:02 +0100, Jim Meyering wrote:
> It should propagate to the public git repo within the hour.

This delay complicates it a bit sometimes for preperation of dependent
patches.  i am not aware of the required + available performance resources but
it could the update run more often?  (if not 1 then for example 5 minutes)


Thanks,
Jan

Re: git update delay [Re: FYI, small patch required to resync git from cvs]

[Jim Meyering]

Jan Kratochvil wrote:
> On Sun, 25 Oct 2009 16:02:02 +0100, Jim Meyering wrote:
>> It should propagate to the public git repo within the hour.
>
> This delay complicates it a bit sometimes for preperation of dependent
> patches.  i am not aware of the required + available performance resources but
> it could the update run more often?  (if not 1 then for example 5 minutes)

Yes, I know how aggravating that can be.
Luckily, the repositories for which I suffered the most have all
converted to git upstream, now ;-)

Currently the gdb cvs-to-git sync process runs once per hour, but a run
can take over 20 minutes when every ,v file has been touched by a tag,
so I can't increase the frequency by much.  Even at the best of times
(I've just confirmed) it takes at least 7 minutes.

I've just doubled its frequency, so now it runs at 8 and 38 minutes
after each hour.

Re: git update delay [Re: FYI, small patch required to resync git from cvs]

[Jan Kratochvil]

On Sun, 25 Oct 2009 16:43:16 +0100, Jim Meyering wrote:
> I've just doubled its frequency, so now it runs at 8 and 38 minutes
> after each hour.

Great, thanks; I thought its local run could be for example just a few secs.


Regards,
Jan

Re: git update delay [Re: FYI, small patch required to resync git from cvs]

[Jim Meyering]

Jan Kratochvil wrote:
> On Sun, 25 Oct 2009 16:43:16 +0100, Jim Meyering wrote:
>> I've just doubled its frequency, so now it runs at 8 and 38 minutes
>> after each hour.
>
> Great, thanks; I thought its local run could be for example just a few secs.

I wish.
Most of the time is spent running cvsps.