syscalltrack-website Mailing List for system call tracker

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

Shlomif,

When you merged outline.text back into HEAD you threw away the link to 
examples.

-- 
Orna.   |  http://tx.technion.ac.il/~agmon

I am here therefore I came.

On Sun, 19 Jan 2003, Muli Ben-Yehuda wrote:

> On Sun, Jan 19, 2003 at 08:14:44PM +0200, Orna Agmon wrote:
>
> > AFAIK, neither I nor Muli authorized this change in HEAD.
> >
> > Shlomi, I hate opening the code and finding undesirable changes in it.
> > I have enough on my head without having to find out if you broke something
> > in HEAD.
>
> Shlomi, please refrain from commiting *anything* to HEAD without prior
> approval from Orna or me. Failure to comply will result in revoking
> your commit priviledges.
>

I am terribly sorry, I did it because I had to merge my changes to the
script with what Orna did, and I made the change automatically. Won't
happen again, but I suggest we use the "use English;" pragma from now on.
It is standard Perl.

Revoking my commit priviliges will make it harder for you to see my
changes, as I can no longer fork my own branches. And since CVS is
centralized (unlike something like BitKeeper) I'll need to maintain my
branches with a local source control system, etc.

Please try to be a little less edgy in regards to me. I am a good guy, and
have no ill intentions. The make_site.pl stuff was a simple automatic
response to de-obfuscate code. I had to integrate my changes with
make_site.pl and so it worked. I think I'll subscribe to sct-commits, and
try to filter only the changes to the web-site.

Now back to work: the main issue with the site is the extremely large (in
KB) image in the front. Given the text of an SCT log, I can easily create
such screenshot and save it in the CVS in a loss-less format for safe
keeping. I can try installing syscalltrack for UML, but I can't promise
anything.

Regards,

	Shlomi Fish

----------------------------------------------------------------------
Shlomi Fish        sh...@vi...
Home Page:         http://t2.technion.ac.il/~shlomif/

He who re-invents the wheel, understands much better how a wheel works.

On Sun, Jan 19, 2003 at 08:14:44PM +0200, Orna Agmon wrote:

> AFAIK, neither I nor Muli authorized this change in HEAD.
> 
> Shlomi, I hate opening the code and finding undesirable changes in it. 
> I have enough on my head without having to find out if you broke something 
> in HEAD.

Shlomi, please refrain from commiting *anything* to HEAD without prior
approval from Orna or me. Failure to comply will result in revoking
your commit priviledges. 
-- 
Muli Ben-Yehuda

http://www.mulix.org

On Sun, 19 Jan 2003, Shlomi Fish wrote:
> 
> 1. The input files are named .txt and so I have to constantly re-highlight
> them as HTML.
> 2. The meta-tags are plaintext: BeginTextHere, BeginHeadHere, etc.
> 3. We will have to work hard to support sub-directories. (WML gives us
> this for free).
> 

WML requires having WML installed.

-- 
Orna.   |  http://tx.technion.ac.il/~agmon

ascii smiles are for weenies. ;-) 
                        -- Muli Ben Yehuda

On Sun, 19 Jan 2003, Shlomi Fish wrote:

> >
> > Regarding examples.txt: It is not broken becasue make_site.pl does not
> > handle links within examples. As I previously said, it is not meant to do
> > that. Examples are text only: computer output. The page that was there is
> > under constraction, waiting for a textual example.
> >
> 
> There was such a link in one of the pages and I had to fix it myself.
> It occurs whenever an HTML tag is broken in the middle. Here's a test
> case:
> 
> <h1>Examples</h1>
> <div class="example">
> BeginExampleHere
> Hallelujah
> <a
>     href="hello">
>     You
>     </a>
> EndExampleHere
> </div>
> 
For the third time, Shlomi: Examples are NOT SUPPOSED TO HAVE LINKS IN 
THEM. Do you read that? Stop bringing me invalid examples for examples 
with 
links in them!

> > AFAIK, neither I nor Muli authorized this change in HEAD.
> >
> > Shlomi, I hate opening the code and finding undesirable changes in it.
> > I have enough on my head without having to find out if you broke something
> > in HEAD.
> >
> 
> I did not break anything. I'm sorry that I changed these obscure variables
> into something more readable. I can change them back if you want. But I
> think that use English; is considered a good idea. I always use it.
> 
What about bugs as the one I gave a link to? I prefer to have things 
stable.

-- 
Orna.   |  http://tx.technion.ac.il/~agmon

ascii smiles are for weenies. ;-) 
                        -- Muli Ben Yehuda

If I can voice my opinion, I think it is a bad idea if all we want to do
is add newlines everywhere. It complicates the code very much. A better
one would be something like:

#includetext "myfile.txt"

where we put in the contents of the file while adding <br /> at the end.

I wish to remind you of the following quote:

<<<
Any sufficiently complicated C or Fortran program contains an ad hoc
informally-specified bug-ridden slow implementation of half of Common
Lisp.

	Phil Greenspun
>>>

As much as I like our current ad-hoc content managament system, it may be
a good idea to take the time and learn Web Meta Language which gives us
for free what will take us monthes to hack on our own. WML is slower, but
it is also much more powerful.

Problems with the current system:

1. The input files are named .txt and so I have to constantly re-highlight
them as HTML.
2. The meta-tags are plaintext: BeginTextHere, BeginHeadHere, etc.
3. We will have to work hard to support sub-directories. (WML gives us
this for free).

Regards,

	Shlomi Fish

----------------------------------------------------------------------
Shlomi Fish        sh...@vi...
Home Page:         http://t2.technion.ac.il/~shlomif/

He who re-invents the wheel, understands much better how a wheel works.

On Sun, 19 Jan 2003, Orna Agmon wrote:

> Shlomi,
>
> I was perfectly fine with $` and $', which are standard perl. The fact
> that you do not know them is not sufficient to allow for you to change
> those in HEAD (into patterns which improve nothing).
>

$POSTMATCH and $PREMATCH are their use English names. When I see such
variables, they confuse the hell out of me. I am familiar with common
variables such as $_, @_, $@, $0, etc. but not with every obscure perl
variable out there. use English is considered a good way to make your code
more readable and maintinable.

>
> Now the Use English part: Aside from the fact that it seems unstable, what
> is the benefit of using this package?
>

That it gives you $POSTMATCH and $PREMATCH.

> http://archive.develooper.com/per...@pe.../msg89633.html
>
> Regarding examples.txt: It is not broken becasue make_site.pl does not
> handle links within examples. As I previously said, it is not meant to do
> that. Examples are text only: computer output. The page that was there is
> under constraction, waiting for a textual example.
>

There was such a link in one of the pages and I had to fix it myself.
It occurs whenever an HTML tag is broken in the middle. Here's a test
case:

<h1>Examples</h1>
<div class="example">
BeginExampleHere
Hallelujah
<a
    href="hello">
    You
    </a>
EndExampleHere
</div>

> AFAIK, neither I nor Muli authorized this change in HEAD.
>
> Shlomi, I hate opening the code and finding undesirable changes in it.
> I have enough on my head without having to find out if you broke something
> in HEAD.
>

I did not break anything. I'm sorry that I changed these obscure variables
into something more readable. I can change them back if you want. But I
think that use English; is considered a good idea. I always use it.

Regards,

	Shlomi Fish

>
>

----------------------------------------------------------------------
Shlomi Fish        sh...@vi...
Home Page:         http://t2.technion.ac.il/~shlomif/

He who re-invents the wheel, understands much better how a wheel works.

Shlomi,

I was perfectly fine with $` and $', which are standard perl. The fact 
that you do not know them is not sufficient to allow for you to change 
those in HEAD (into patterns which improve nothing). 

Now the Use English part: Aside from the fact that it seems unstable, what 
is the benefit of using this package?

http://archive.develooper.com/per...@pe.../msg89633.html

Regarding examples.txt: It is not broken becasue make_site.pl does not 
handle links within examples. As I previously said, it is not meant to do 
that. Examples are text only: computer output. The page that was there is 
under constraction, waiting for a textual example.

AFAIK, neither I nor Muli authorized this change in HEAD.

Shlomi, I hate opening the code and finding undesirable changes in it. 
I have enough on my head without having to find out if you broke something 
in HEAD.

-- 
Orna.   |  http://tx.technion.ac.il/~agmon

ascii smiles are for weenies. ;-) 
                        -- Muli Ben Yehuda

On Sat, 18 Jan 2003, Muli Ben-Yehuda wrote:

> On Sat, Jan 18, 2003 at 11:07:50PM +0200, Orna Agmon wrote:
> > On Sat, 18 Jan 2003, Shlomi Fish wrote:
> > >
> > > Whatever, but merging two different branches is not always
> > > straightforward, especially with all the resultant HTMLs kept there.
> >
> > Release Early, Release Often.
>
> Shlomi, the onus on tracking HEAD changes is on you. I've told you
> before: your branches are considered experimental, and therefore are
> expected to track HEAD. This is in contrast with the situation where
> HEAD is stable, and the development occurs in branches. In this case,
> development occurs in HEAD (by Orna, and me very very occasionally),
> and your branches are experimental, to-be-merged-as-we-see-fit.
>
> If you feel you can't work within these guidelines, feel free to
> cease.
>

Understood. I'll just have to adapt to the new modus operandi. Is it
possible to subscribe to the commits lists and filter only the ones that
occured under wwwdocs/ ? (I suppose procmail can do it. Procmail can do
anything...)

Regards,

	Shlomi Fish

----------------------------------------------------------------------
Shlomi Fish        sh...@vi...
Home Page:         http://t2.technion.ac.il/~shlomif/

He who re-invents the wheel, understands much better how a wheel works.

On Sat, Jan 18, 2003 at 11:07:50PM +0200, Orna Agmon wrote:
> On Sat, 18 Jan 2003, Shlomi Fish wrote:
> > 
> > Whatever, but merging two different branches is not always
> > straightforward, especially with all the resultant HTMLs kept there.
> 
> Release Early, Release Often.

Shlomi, the onus on tracking HEAD changes is on you. I've told you
before: your branches are considered experimental, and therefore are
expected to track HEAD. This is in contrast with the situation where
HEAD is stable, and the development occurs in branches. In this case,
development occurs in HEAD (by Orna, and me very very occasionally),
and your branches are experimental, to-be-merged-as-we-see-fit. 

If you feel you can't work within these guidelines, feel free to
cease. 
-- 
Muli Ben-Yehuda

http://www.mulix.org

On Sat, 18 Jan 2003, Shlomi Fish wrote:
> 
> Whatever, but merging two different branches is not always
> straightforward, especially with all the resultant HTMLs kept there.

Release Early, Release Often.
> I checked it and it does. I had to place the entire <a > tag on one place.

Give me the exact example.

-- 
Orna.   |  http://tx.technion.ac.il/~agmon

ascii smiles are for weenies. ;-) 
                        -- Muli Ben Yehuda

On Sat, 18 Jan 2003, Orna Agmon wrote:

> On Sat, 18 Jan 2003, Shlomi Fish wrote:
>
> > > You can MERGE your branch into HEAD, but not make it HEAD, since there are
> > > some files which are older in your branch (at least make_site.pl,
> > > outline.text, sctstyle.css) and examples.(txt, html) does not exist.
> > >
> > > And while you are at it, removing the ^M marks would be nice.
> > >
> >
> > Done and done. Next time please work on the development branch (which I
> > announce here on the mailing list).
>
>
> No, the development branches are yours. Please synchronize them.
>

Whatever, but merging two different branches is not always
straightforward, especially with all the resultant HTMLs kept there.

> >
> > BTW, the make_site.pl breaks if HTML tags occupy several lines. I.e:
> >
> > <a href="hello"
> > 	target="good">
> >
> > Will turn into:
> > <a href="hello" <br />
> >  	target="good">
>
> No, it does not. Have you checked this? the <br/> tags are only
> added between the example boundaries, which should not contain links but
> only text.
>

I checked it and it does. I had to place the entire <a > tag on one place.

> and deleting your long, non "-- " signature is rather tiring.
>
>

It's not very long (only a horizonal rule and 4 lines)

Regards,

	Shlomi Fish

----------------------------------------------------------------------
Shlomi Fish        sh...@vi...
Home Page:         http://t2.technion.ac.il/~shlomif/

He who re-invents the wheel, understands much better how a wheel works.

On Sat, 18 Jan 2003, Shlomi Fish wrote:

> > You can MERGE your branch into HEAD, but not make it HEAD, since there are
> > some files which are older in your branch (at least make_site.pl,
> > outline.text, sctstyle.css) and examples.(txt, html) does not exist.
> >
> > And while you are at it, removing the ^M marks would be nice.
> >
> 
> Done and done. Next time please work on the development branch (which I
> announce here on the mailing list).

No, the development branches are yours. Please synchronize them.

> 
> BTW, the make_site.pl breaks if HTML tags occupy several lines. I.e:
> 
> <a href="hello"
> 	target="good">
> 
> Will turn into:
> <a href="hello" <br />
>  	target="good">

No, it does not. Have you checked this? the <br/> tags are only 
added between the example boundaries, which should not contain links but 
only text.

and deleting your long, non "-- " signature is rather tiring.

-- 
Orna.   |  http://tx.technion.ac.il/~agmon

ascii smiles are for weenies. ;-) 
                        -- Muli Ben Yehuda

On Sat, Jan 18, 2003 at 05:52:32AM +0200, Shlomi Fish wrote:
> On Sat, 11 Jan 2003, Muli Ben-Yehuda wrote:
> 
> > On Sat, Jan 11, 2003 at 10:48:07AM +0200, Shlomi Fish wrote:
> >
> > > 2. Secondly, should I edit the changelog directly, or do I need to use
> > > some tool for that. Muli mentioned some Perl script he got and wrote
> > > another python script to wrap it. Do I need them?
> >
> > I use a script called make-changelog.pl, you can google for it. You
> > don't have to use it if you don't want to, just maintain the same
> > format.
> >
> 
> Muli, the only Google entry for it is your Python lecture. Can you please
> send it to me. (gzip it if it's too large or put it in the CVS somewhere
> like under /utils)

Attached. 

#!/usr/bin/perl -w
# -*- Mode: perl; indent-tabs-mode: nil; c-basic-offset: 2  -*-

# Perl script to create a ChangeLog entry with names of files
# and functions from a cvs diff.
#
# Darin Adler <da...@ea...>, started 20 April 2000
# last updated 15 May 2000
#
# (Someone put a license in here, like maybe GPL.)
#
# TODO:
#   Provide option to put new ChangeLog into a separate file
#     instead of editing the ChangeLog.
#   For new files, just say "New file" instead of listing
#     function names.
#   List functions that have been removed too.
#   Decide what a good logical order is for the changed files
#     other than a normal text "sort" (top level first?)
#     (group directories?) (.h before .c?)
#   Leave a diff file behind if asked, but in unified format.
#   Handle C++ and yacc source files too (other languages?).
#   Help merge when there are ChangeLog conflicts or if there's
#     already a partly written ChangeLog entry.
#   Find appropriate ChangeLog to edit for each changed file
#     instead of always using ChangeLog in current directory.
#   Add command line option to put the ChangeLog into a separate
#     file or just spew it out stdout.
#   Figure out how to allow -z options from .cvsrc to work without
#     letting other bad options work. Currently the -f disables
#     everything from the .cvsrc.
#   Add CVS version numbers for each file too (can't do that until
#     the changes are checked in, though).
#   Work around diff stupidity where deleting a function that starts
#     with a comment makes diff think that the following function
#     has been changed (if the following function starts with a comment
#     with the same first line, such as /**)
#   Work around diff stupidity where deleting an entire function and
#     the blank lines before it makes diff think you've changed the
#     previous function.

use diagnostics;
use strict;

use English;
use Text::Wrap;

# Read the old change log file.
# It's less efficient to read the whole thing into memory than it would be
# to read it while we prepend to it later, but I like doing this part first.
print STDERR "  Updating ChangeLog from cvs repository.\n";
open ERRORS, "cvs update ChangeLog |" or die "The cvs update of ChangeLog failed: $OS_ERROR.\n";
print STDERR "    $ARG" while <ERRORS>;
close ERRORS;
open OLD_CHANGE_LOG, "ChangeLog" or die "Could not open ChangeLog file: $OS_ERROR.\n";
my @old_change_log = <OLD_CHANGE_LOG>;
close OLD_CHANGE_LOG;

# For each file, build a list of modified lines.
# Use line numbers from the "after" side of each diff.
print STDERR "  Running cvs diff to find changes.\n";
my %changed_line_ranges;
my $file;
open DIFF, "cvs -fq diff -N |" or die "The cvs diff failed: $OS_ERROR.\n";
while (<DIFF>)
  {
    $file = $1 if /^Index: (\S+)$/;
    if (defined $file
        and $file ne "ChangeLog"
        and /^\d+(,\d+)?[acd](\d+)(,(\d+))?/)
      {
        push @{$changed_line_ranges{$file}}, [ $2, $4 || $2 ];
      }
  }
close DIFF;
if (!%changed_line_ranges)
  {
    print STDERR "  No changes found.\n";
    exit;
  }

# For each ".c" file, convert line range to function list.
print STDERR "  Extracting affected function names from C source files.\n";
my %function_lists;
foreach my $file (keys %changed_line_ranges)
  {
    # An empty function list still indicates that something changed.
    $function_lists{$file} = "";

    # Only look for function names in .c files.
    next unless $file =~ /\.c$/;

    # Find all the functions in the file.
    open SOURCE, $file or next;
    my @function_ranges = get_function_line_ranges(\*SOURCE);
    close SOURCE;

    # Find all the modified functions.
    my @functions;
    my @change_ranges = (@{$changed_line_ranges{$file}}, []);
    my @change_range = (0, 0);
    FUNCTION: foreach my $function_range_ref (@function_ranges)
      {
        my @function_range = @$function_range_ref;

        # Advance to successive change ranges.
        for (;; @change_range = @{shift @change_ranges})
          {
            last FUNCTION unless @change_range;

            # If past this function, move on to the next one.
            next FUNCTION if $change_range[0] > $function_range[1];

            # If an overlap with this function range, record the function name.
            if ($change_range[1] >= $function_range[0]
                and $change_range[0] <= $function_range[1])
              {
                push @functions, $function_range[2];
                next FUNCTION;
              }
          }
      }

    # Format the list of functions now.
    $function_lists{$file} = " (" . join("), (", @functions) . "):" if @functions;
  }

# Write out a new ChangeLog file.
print STDERR "  Editing the ChangeLog file.\n";
my $date = sprintf "%d-%02d-%02d %02d:%02d:%02d",
  1900 + (localtime $BASETIME)[5], # year
  1 + (localtime $BASETIME)[4], # month
  (localtime $BASETIME)[3], # day within month
  (localtime $BASETIME)[2], # hour
  (localtime $BASETIME)[1], # min
  (localtime $BASETIME)[0]; # sec
my $name = $ENV{CHANGE_LOG_NAME}
  || $ENV{REAL_NAME}
  || (getpwuid $REAL_USER_ID)[6]
  || "set REAL_NAME environment variable";
my $email_address = $ENV{CHANGE_LOG_EMAIL_ADDRESS}
  || $ENV{EMAIL_ADDRESS}
  || "set EMAIL_ADDRESS environment variable";
open CHANGE_LOG, "> ChangeLog" or die "Could not write ChangeLog\n.";
print CHANGE_LOG "$date  $name  <$email_address>\n\n";
foreach my $file (sort keys %function_lists)
  {
    my $lines = wrap("\t", "\t", "XX$file:$function_lists{$file}");
    $lines =~ s/^\tXX/\t* /;
    print CHANGE_LOG "$lines\n";
  }
print CHANGE_LOG "\n", @old_change_log;
close CHANGE_LOG;

# Done.
print STDERR "  Done editing ChangeLog.\n";
exit;

# Read a file and get all the line ranges of the things that look like C functions.
# A function name is the last word before an open parenthesis before the outer
# level open brace. A function starts at the first character after the last close
# brace or semicolon before the function name and ends at the close brace.
# Comment handling is simple-minded but will work for all but pathological cases.
#
# Result is a list of triples: [ start_line, end_line, function_name ].

sub get_function_line_ranges
  {
    my $file_handle = shift;

    my @ranges;

    my $in_comment = 0;
    my $in_macro = 0;
    my $in_parentheses = 0;
    my $in_braces = 0;

    my $word = "";

    my $potential_start = 0;
    my $potential_name = "";

    my $start = 0;
    my $name = "";

    while (<$file_handle>)
      {
        # Handle continued multi-line comment.
        if ($in_comment)
          {
            next unless s-.*\*/--;
            $in_comment = 0;
          }

        # Handle continued macro.
        if ($in_macro)
          {
            $in_macro = 0 unless /\\$/;
            next;
          }

        # Handle start of macro (or any preprocessor directive).
        if (/^\s*\#/)
          {
            $in_macro = 1 if /^([^\\]|\\.)*\\$/;
            next;
          }

        # Handle comments and quoted text.
        while (m-(/\*|//|\'|\")-) # \' and \" keep emacs perl mode happy
          {
            my $match = $1;
            if ($match eq "/*")
              {
                if (!s-/\*.*?\*/--)
                  {
                    s-/\*.*--;
                    $in_comment = 1;
                  }
              }
            elsif ($match eq "//")
              {
                s-//.*--;
              }
            else # ' or "
              {
                if (!s-$match([^\\]|\\.)*?$match--)
                  {
                    warn "mismatched quotes";
                    s-$match.*--;
                  }
              }
          }

        # Find function names.
        while (m-(\w+|[(){};])-g)
          {
            # Open parenthesis.
            if ($1 eq "(")
              {
                $potential_name = $word unless $in_parentheses;
                $in_parentheses++;
                next;
              }

            # Close parenthesis.
            if ($1 eq ")")
              {
                $in_parentheses--;
                next;
              }

            # Open brace.
            if ($1 eq "{")
              {
                # Promote potiential name to real function name at the
                # start of the outer level set of braces (function body?).
                if (!$in_braces and $potential_start)
                  {
                    $start = $potential_start;
                    $name = $potential_name;
                  }

                $in_braces++;
                next;
              }

            # Close brace.
            if ($1 eq "}")
              {
                $in_braces--;

                # End of an outer level set of braces.
                # This could be a function body.
                if (!$in_braces and $name)
                  {
                    push @ranges, [ $start, $INPUT_LINE_NUMBER, $name ];
                    $name = "";
                  }

                $potential_start = 0;
                $potential_name = "";
                next;
              }

            # Semicolon.
            if ($1 eq ";")
              {
                $potential_start = 0;
                $potential_name = "";
                next;
              }

            # Word.
            $word = $1;
            if (!$in_parentheses)
              {
                $potential_start = 0;
                $potential_name = "";
              }
            if (!$potential_start)
              {
                $potential_start = $INPUT_LINE_NUMBER;
                $potential_name = "";
              }
          }
      }

    warn "mismatched braces" if $in_braces;
    warn "mismatched parentheses" if $in_parentheses;

    return @ranges;
  }
-- 
Muli Ben-Yehuda

http://www.mulix.org

On Sat, 18 Jan 2003, Orna Agmon wrote:

> On Fri, 17 Jan 2003, Shlomi Fish wrote:
>
> >
> > The XHTML/1.0 Transitional version of the site is working and stable and
> > looks good on all browsers I checked (Konq, MSIE, Mozilla and Opera).
> > However, there is still the issue of the large screenshot which has been
> > compressed as jpeg and so got a lot of noise.
> >
> > We can either wait for the new screenshot (which should be in PNG or even
> > in text format (copy and paste from a terminal)) or we can publish the
> > site now with the current issue present.
> >
> > I say publish now, since the older site has this problem as well.
> >
> > Let me know what you think.
>
> You can MERGE your branch into HEAD, but not make it HEAD, since there are
> some files which are older in your branch (at least make_site.pl,
> outline.text, sctstyle.css) and examples.(txt, html) does not exist.
>
> And while you are at it, removing the ^M marks would be nice.
>

Done and done. Next time please work on the development branch (which I
announce here on the mailing list).

BTW, the make_site.pl breaks if HTML tags occupy several lines. I.e:

<a href="hello"
	target="good">

Will turn into:
<a href="hello" <br />
 	target="good">

Regards,

	Shlomi Fish

>
>

----------------------------------------------------------------------
Shlomi Fish        sh...@vi...
Home Page:         http://t2.technion.ac.il/~shlomif/

He who re-invents the wheel, understands much better how a wheel works.

On Sat, 11 Jan 2003, Muli Ben-Yehuda wrote:

> On Sat, Jan 11, 2003 at 10:48:07AM +0200, Shlomi Fish wrote:
>
> > 2. Secondly, should I edit the changelog directly, or do I need to use
> > some tool for that. Muli mentioned some Perl script he got and wrote
> > another python script to wrap it. Do I need them?
>
> I use a script called make-changelog.pl, you can google for it. You
> don't have to use it if you don't want to, just maintain the same
> format.
>

Muli, the only Google entry for it is your Python lecture. Can you please
send it to me. (gzip it if it's too large or put it in the CVS somewhere
like under /utils)

Regards,

	Shlomi Fish

----------------------------------------------------------------------
Shlomi Fish        sh...@vi...
Home Page:         http://t2.technion.ac.il/~shlomif/

He who re-invents the wheel, understands much better how a wheel works.

On Fri, 17 Jan 2003, Shlomi Fish wrote:

> 
> The XHTML/1.0 Transitional version of the site is working and stable and
> looks good on all browsers I checked (Konq, MSIE, Mozilla and Opera).
> However, there is still the issue of the large screenshot which has been
> compressed as jpeg and so got a lot of noise.
> 
> We can either wait for the new screenshot (which should be in PNG or even
> in text format (copy and paste from a terminal)) or we can publish the
> site now with the current issue present.
> 
> I say publish now, since the older site has this problem as well.
> 
> Let me know what you think.

You can MERGE your branch into HEAD, but not make it HEAD, since there are 
some files which are older in your branch (at least make_site.pl, 
outline.text, sctstyle.css) and examples.(txt, html) does not exist.

And while you are at it, removing the ^M marks would be nice.

-- 
Orna.   |  http://tx.technion.ac.il/~agmon

ascii smiles are for weenies. ;-) 
                        -- Muli Ben Yehuda

On Tue, 14 Jan 2003, Shlomi Fish wrote:

> 
> Looks nice. Very nice.
> 
> Opera seems like a nice browser with a lot of usability features. I had to
> download the version that is statically linked with Qt (even though I have

version of what? if you refer to the Opera version, why does it matter? If 
you refer to the site, then the CVS does not match the site currently, as 
we are waiting for a trace example to fit in the new examples page.

> KDE running) because in Mandrake it is names qt-mt, and opera does not
> like it.
> 
> But we have another browser to use. The site looks differently (i.e: not
> "exactly" the same) but the main things are identical.
> 

> Now, Muli can you provide me with another screenshot?
> 
> Regards,
> 
> 	Shlomi Fish
> 
> 
> ----------------------------------------------------------------------
> Shlomi Fish        sh...@vi...
> Home Page:         http://t2.technion.ac.il/~shlomif/
> 
> He who re-invents the wheel, understands much better how a wheel works.
> 
> 
> 
> -------------------------------------------------------
> This SF.NET email is sponsored by: FREE  SSL Guide from Thawte
> are you planning your Web Server Security? Click here to get a FREE
> Thawte SSL guide and find the answers to all your  SSL security issues.
> http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
> _______________________________________________
> Syscalltrack-website mailing list
> Sys...@li...
> https://lists.sourceforge.net/lists/listinfo/syscalltrack-website
> 

-- 
Orna.   |  http://tx.technion.ac.il/~agmon

ascii smiles are for weenies. ;-) 
                        -- Muli Ben Yehuda

I cannot find any ChangeLog entry for your last branch.

On Tue, 14 Jan 2003, Shlomi Fish wrote:

> 
> Looks nice. Very nice.
> 
> Opera seems like a nice browser with a lot of usability features. I had to
> download the version that is statically linked with Qt (even though I have
> KDE running) because in Mandrake it is names qt-mt, and opera does not
> like it.
> 
> But we have another browser to use. The site looks differently (i.e: not
> "exactly" the same) but the main things are identical.
> 
> Now, Muli can you provide me with another screenshot?
> 
> Regards,
> 
> 	Shlomi Fish
> 
> 
> ----------------------------------------------------------------------
> Shlomi Fish        sh...@vi...
> Home Page:         http://t2.technion.ac.il/~shlomif/
> 
> He who re-invents the wheel, understands much better how a wheel works.
> 
> 
> 
> -------------------------------------------------------
> This SF.NET email is sponsored by: FREE  SSL Guide from Thawte
> are you planning your Web Server Security? Click here to get a FREE
> Thawte SSL guide and find the answers to all your  SSL security issues.
> http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
> _______________________________________________
> Syscalltrack-website mailing list
> Sys...@li...
> https://lists.sourceforge.net/lists/listinfo/syscalltrack-website
> 

-- 
Orna.   |  http://tx.technion.ac.il/~agmon

ascii smiles are for weenies. ;-) 
                        -- Muli Ben Yehuda

The XHTML/1.0 Transitional version of the site is working and stable and
looks good on all browsers I checked (Konq, MSIE, Mozilla and Opera).
However, there is still the issue of the large screenshot which has been
compressed as jpeg and so got a lot of noise.

We can either wait for the new screenshot (which should be in PNG or even
in text format (copy and paste from a terminal)) or we can publish the
site now with the current issue present.

I say publish now, since the older site has this problem as well.

Let me know what you think.

Regards,

	Shlomi Fish

----------------------------------------------------------------------
Shlomi Fish        sh...@vi...
Home Page:         http://t2.technion.ac.il/~shlomif/

He who re-invents the wheel, understands much better how a wheel works.

Looks nice. Very nice.

Opera seems like a nice browser with a lot of usability features. I had to
download the version that is statically linked with Qt (even though I have
KDE running) because in Mandrake it is names qt-mt, and opera does not
like it.

But we have another browser to use. The site looks differently (i.e: not
"exactly" the same) but the main things are identical.

Now, Muli can you provide me with another screenshot?

Regards,

	Shlomi Fish

----------------------------------------------------------------------
Shlomi Fish        sh...@vi...
Home Page:         http://t2.technion.ac.il/~shlomif/

He who re-invents the wheel, understands much better how a wheel works.

On Sat, 11 Jan 2003, Muli Ben-Yehuda wrote:

> On Sat, Jan 11, 2003 at 10:48:07AM +0200, Shlomi Fish wrote:
>
> > 2. Secondly, should I edit the changelog directly, or do I need to use
> > some tool for that. Muli mentioned some Perl script he got and wrote
> > another python script to wrap it. Do I need them?
>
> I use a script called make-changelog.pl, you can google for it. You
> don't have to use it if you don't want to, just maintain the same
> format.
>

Acknowledged. Thanks. I will. (I only take orders and fullfill them in the
worst possible way)

Regards,

	Shlomi Fish

----------------------------------------------------------------------
Shlomi Fish        sh...@vi...
Home Page:         http://t2.technion.ac.il/~shlomif/

He who re-invents the wheel, understands much better how a wheel works.

On Sat, Jan 11, 2003 at 10:48:07AM +0200, Shlomi Fish wrote:

> 2. Secondly, should I edit the changelog directly, or do I need to use
> some tool for that. Muli mentioned some Perl script he got and wrote
> another python script to wrap it. Do I need them?

I use a script called make-changelog.pl, you can google for it. You
don't have to use it if you don't want to, just maintain the same
format. 
-- 
Muli Ben-Yehuda

my opinions may seem crazy. But they all make sense. Insane sense, but
sense nontheless. -- Shlomi Fish on #offtopic.

On Fri, 10 Jan 2003, Orna Agmon wrote:

> ChangeLog is there to keep the record of the changes done to the module.
> Shlomi, you entered a change to make_site.pl (the EnterTitleHere change),
> without making a note of it in the ChangeLog. Please make sure to always
> make a ChangeLog entry (unless it is a branch you are the only one who
> works on). CVS commit messages are not enough.
>

Very well. Two comments:

1. First of all there's cvsps: (short for CVS Patchsets)

http://www.cobite.com/cvsps/

That summarizes the common commit remark for several files. It is very
nice.

2. Secondly, should I edit the changelog directly, or do I need to use
some tool for that. Muli mentioned some Perl script he got and wrote
another python script to wrap it. Do I need them?

Regards,

	Shlomi Fish

 >

----------------------------------------------------------------------
Shlomi Fish        sh...@vi...
Home Page:         http://t2.technion.ac.il/~shlomif/

He who re-invents the wheel, understands much better how a wheel works.

ChangeLog is there to keep the record of the changes done to the module.
Shlomi, you entered a change to make_site.pl (the EnterTitleHere change),
without making a note of it in the ChangeLog. Please make sure to always 
make a ChangeLog entry (unless it is a branch you are the only one who 
works on). CVS commit messages are not enough.

-- 
Orna.   |  http://tx.technion.ac.il/~agmon

Had God wanted to create the world efficiently,
she would have used LaTeX.

syscalltrack-website Mailing List for system call tracker

syscalltrack-website — discussions of the syscalltrack website