Jeff, general comment: can you please send your patches as replies
to a leading message so they all be linked as a single thread?
Threading them together is helpful for maintaining several
versions of your patchset and it's simpler to ignore if one's
not really interested in this topic at all.
I was already scolded about this by a few folks. I had not located the
git email programs when I submitted this project and I wrote something
myself to submit them. (see attached). I have thrown the program in the
trash I wrote to do this and moved to git.
Now I have reviewed the git clients and patch tools and I understand and
will use git and I see now why git works this way with the reply chain. I
will not be submitting patch series on this list for every release unless
the code has had major additions or changes in the future. I will
instead post the patches to the project site with a single post on this
list to point to the patches.
I will post patch series when x86_64 is finished and I have completed my
rewrite of traps_32.c and traps_64.c -- Linux needs nested TSS gates over
all the exceptions so the system can handle nested exceptions and switch
to a known good stack during faults. At present, what's there is ok but
not as resilient as it could be.
#define TESTING 1
unsigned char buffer;
unsigned char filename;
int output_comments(FILE *fl, int j)
int main(int argc, char *argv)
register int i = 1, j;
register FILE *fp = NULL, *fl, *fs;
char *s, *p;
while (s = fgets(buffer, 8192, stdin))
if (!strncmp(s, "diff", 4))
if (!strncmp(s, "---", 3))
sprintf(filename, "%i.patch", i);
fp = fopen(filename, "wb");
printf("file open error [%s]\n", filename);
p = strchr(s, '/');
fprintf(fp, "--- a");
fprintf(fp, "%s", p);
fprintf(fp, "%s", s);