, [EMAIL
PROTECTED]
Stephen R. van den Berg (AKA BuGless).
I hate spinach, and I'm glad that I hate it, because if I wouldn't hate it,
I would have to eat it, and I hate it!
H. William Welliver III wrote:
That should be fixed now. There is no client_rsa if you're not using
certificates.
Fixed since?
--
Sincerely, [EMAIL
PROTECTED]
Stephen R. van den Berg (AKA BuGless).
Good moaning!
, [EMAIL
PROTECTED]
Stephen R. van den Berg (AKA BuGless).
Good moaning!
?
--
Sincerely, [EMAIL
PROTECTED]
Stephen R. van den Berg (AKA BuGless).
Good moaning!
).
--
Sincerely, [EMAIL
PROTECTED]
Stephen R. van den Berg (AKA BuGless).
Good moaning!
Stephen R. van den Berg wrote:
For a tiny bit of Pike promotion, and to show that the community is
Ah yes, before I forget, in order to get them to actually recognise Pike
and RXML as a separate language, you'd have to contribute code to:
http://labs.ohloh.net/ohcount
which detects
utimbuf b;
+#endif
#ifdef PIKE_SECURITY
if(!CHECK_SECURITY(SECURITY_BIT_SECURITY))
--
1.5.4.3
--
Sincerely, [EMAIL
PROTECTED]
Stephen R. van den Berg (AKA BuGless).
Am I paying for this abuse or is it extra?
has?
E.g. int somefunc(int __attribute__(unused) level, int depth) { }
in order to suppress warnings for int level.
--
Sincerely, [EMAIL
PROTECTED]
Stephen R. van den Berg.
A sign seen at the local pizza place: DO NOT CARRY
, [EMAIL
PROTECTED]
Stephen R. van den Berg.
Technology is stuff that doesn't work yet. -- Bran Ferren
We no longer think of chairs as technology. -- Douglas Adams
presume the latter. Could the timestamp on the module have been
off because of inadvertent backward system time corrections?
Is the file on a remote filesystem with clock skew relative to the
server running Pike/Roxen?
--
Sincerely,
Stephen R. van den Berg.
Life is that brief interlude
actually overwrites the physical memory location content with zeroes first
(before releasing to the garbage collector).
--
Sincerely,
Stephen R. van den Berg.
You are confused; but this is your normal state.
of the program and then fishing out all the
strings), and then using all the found strings to launch an attack
is likely to succeed in a shorter time than doing a full brute-force
attack, and therefore is weaker than not having the string visible at
all.
--
Sincerely,
Stephen R. van den Berg
this
marker to suppress casual display of the string, then if this string
just happens to be the same as some other (unsecured) string, then the
printing of the unsecured string is going to be prohibited as well (all
of a sudden), which is confusing at best.
--
Sincerely,
Stephen R. van
. van den Berg.
Warning: Dates in calendar are closer than they appear.
buffering (which is what I need to
do if we want to back out the addition).
--
Sincerely,
Stephen R. van den Berg.
Your complaint will be ignored in the order in which it was received.
it to unread, and wait for comments from the rest
here.
? @seealso is now incomplete for all the other related functions.
I'll check it.
--
Sincerely,
Stephen R. van den Berg.
Insanity is a gradual process; don't rush it.
Stephen R. van den Berg wrote:
Peter Bortas @ Pike developers forum wrote:
That's the information I'd like to see now _on the list_ before each
checkin that changes behaviour. I know you are doing good work with
the Postgres bindings, and I will continue to turn a blind eye to
that.
Well, I have
Author: Stephen R. van den Berg [EMAIL PROTECTED]
Date: Mon Jul 14 12:47:28 2008 +0200
Make getchar() less filling, and inlinable
diff --git a/lib/modules/Stdio.pmod/module.pmod
b/lib/modules/Stdio.pmod/module.pmod
index 8edf78b..fa4aacd 100644
--- a/lib/modules/Stdio.pmod/module.pmod
+++ b
Stephen R. van den Berg wrote:
Stephen R. van den Berg wrote:
Peter Bortas @ Pike developers forum wrote:
Well, I have fixed and brushed up the existing Postgres driver as much as I
needed for the short term (it is stable in its current form and heavily tested
in a production environment, I don't
Why is this affected_rows() part of the connection class of a database, and not
part of the result class (where it belongs, IMO)?
--
Sincerely,
Stephen R. van den Berg.
Question = to ? be : !be
H. William Welliver III wrote:
What would be really nifty would be a mode whereby you could access
the node tree for a program and query it. That would enable all kinds
of very powerful program manipulation.
Lisp, eat your heart out! ;-)
--
Sincerely,
Stephen R. van den Berg.
I
that they shouldn't zap the buffers at EOF?
Excuse me for asking, but what do you need the state for?
Basically, all that's needed is that a seek() resets the
state into something that can be used.
--
Sincerely,
Stephen R. van den Berg.
Always remember that you are unique. Just like everyone
it at about 100% (or
greater) of the libpq speed though.
--
Sincerely,
Stephen R. van den Berg.
Expect the unexpected!
it something like _pgsql/_pgsql.cmod
instead?
It's a class that is not meant to be called by anyone besides my
Sql/pgsql.pike driver.
--
Sincerely,
Stephen R. van den Berg.
Climate is what you expect. Weather is what you get.
to create a new branch
which I then commit to several times, and then at the end, I merge all
changes at once into CVS (and destroy my local development branch for
this feature/bugfix).
--
Sincerely,
Stephen R. van den Berg.
Well, if we're going to make a party of it, let's nibble Nobby's
,
Stephen R. van den Berg.
Well, if we're going to make a party of it, let's nibble Nobby's nuts!
decodedatarow() ?
--
Sincerely,
Stephen R. van den Berg.
Well, if we're going to make a party of it, let's nibble Nobby's nuts!
Stephen R. van den Berg wrote:
PIKEFUN array decodedatarow(int msglen, object portal) {
class portal {
int a;
int b;
};
After digging through the Pike sources, the best I can come up with
is something like:
safe_apply(portal,a,0);
But that doesn't seem right, and it also doesn't tell me
Can anyone tell me when a module belongs in post_modules instead of
modules?
--
Sincerely,
Stephen R. van den Berg.
Well, if we're going to make a party of it, let's nibble Nobby's nuts!
-identification project will make the final
strides.
--
Sincerely,
Stephen R. van den Berg.
Well, if we're going to make a party of it, let's nibble Nobby's nuts!
, MK_STRING_SVALUE(_datarows), Pike_sp-1);
Pike_sp--;
I realise that I need to run pop_stack() at the end instead, but that
still leaves me puzzled about the efficient append.
--
Sincerely,
Stephen R. van den Berg.
Well, if we're going to make a party of it, let's nibble Nobby's nuts!
,
Stephen R. van den Berg.
Well, if we're going to make a party of it, let's nibble Nobby's nuts!
the portability code in full from files/file.c into
the PGsql driver, so it should work just fine on Windows now.
I wanted to check just once, and if it doesn't get a green light,
disable the module for compilation.
--
Sincerely,
Stephen R. van den Berg.
Well, if we're going to make a party
, MK_STRING_SVALUE(_datarows), Pike_sp-1);
pop_stack();
Because, as it turns out, in most cases, the array is empty before we
start.
--
Sincerely,
Stephen R. van den Berg.
Well, if we're going to make a party of it, let's nibble Nobby's nuts!
Stephen R. van den Berg wrote:
I've been working on a PGsql helper class to speed up the hotspots
in my new pgsql PostgreSQL driver; so far it works rather well, and
the performance of the new driver has leaped from 10% of the libpq
module, to about 45% of the libpq module.
Well, I'm pleased
Stephen R. van den Berg wrote:
Stephen R. van den Berg wrote:
I've been working on a PGsql helper class to speed up the hotspots
in my new pgsql PostgreSQL driver; so far it works rather well, and
the performance of the new driver has leaped from 10% of the libpq
module, to about 45% of the libpq
Stephen R. van den Berg wrote:
And I (sadly) had to disable the module for now, because it still seems
to be causing problems on Windows.
Anyone capable of fetching me the error log?
Sorry for the noise. Figured out I could retrieve the error logs
through the farm interface.
--
Sincerely
);
if(ret 0)
{
It's a 40% speed difference caused by extra latency in the pgsql driver
case.
--
Sincerely,
Stephen R. van den Berg.
Very funny, Mr. Scott. Now beam down my clothes!
the file, alter the content, then commit, most of the time
git gets it right.
--
Sincerely,
Stephen R. van den Berg.
Very funny, Mr. Scott. Now beam down my clothes!
Peter Bortas @ Pike developers forum wrote:
The script is not exporting again so Stephen never saw my answer. Can
I have the script so I can set it up on the Pike computer instead?
Any other answers I missed? How about the poll/file_peek issue?
--
Sincerely,
Stephen R. van den Berg
of backlog mails (around 12,
starting last Tuesday).
--
Sincerely,
Stephen R. van den Berg.
Very funny, Mr. Scott. Now beam down my clothes!
() to call them.
--
Sincerely,
Stephen R. van den Berg.
Very funny, Mr. Scott. Now beam down my clothes!
ref_push_string and the same for push_object vs.
ref_push_object which take time to figure out.
--
Sincerely,
Stephen R. van den Berg.
Very funny, Mr. Scott. Now beam down my clothes!
the implications of the three rename
cases I listed before.
--
Sincerely,
Stephen R. van den Berg.
Very funny, Mr. Scott. Now beam down my clothes!
into README and README-CVS. Can git handle that and retain
a common ancestry for both files?
Yes. No problem whatsoever.
--
Sincerely,
Stephen R. van den Berg.
Very funny, Mr. Scott. Now beam down my clothes!
the file existed before (as you
normally would), then git retains a parent pointer to that older
version, and hence has complete history/ancestry/annotation available.
--
Sincerely,
Stephen R. van den Berg.
Very funny, Mr. Scott. Now beam down my clothes!
Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) @ Pike (-) developers forum wrote:
How do you do it? I could not find any git cp command.
Simply copy the file using a normal cp, then git add it, and git will
pick it up automatically.
--
Sincerely,
Stephen R. van den Berg.
Very funny, Mr
.
--
Sincerely,
Stephen R. van den Berg.
Very funny, Mr. Scott. Now beam down my clothes!
reference to f2542cf, it will know where the
file(s) came from and will retain history, regardless of old and new
locations in the tree.
--
Sincerely,
Stephen R. van den Berg.
Very funny, Mr. Scott. Now beam down my clothes!
, this problem
rarely arises.
--
Sincerely,
Stephen R. van den Berg.
Very funny, Mr. Scott. Now beam down my clothes!
.
--
Sincerely,
Stephen R. van den Berg.
Very funny, Mr. Scott. Now beam down my clothes!
?
Git has the information you want to see; I'm not completely certain what
you mean by accurate information, but the information is either shown
already, or can be revealed with the proper options turned on.
--
Sincerely,
Stephen R. van den Berg.
Very funny, Mr. Scott. Now beam down my
).
Incidentally, it's these silly things like, when to use push_string or
when to use ref_push_string and the same for push_object vs.
ref_push_object which take time to figure out.
Yes. :p
And the coredumps that follow don't really give enough clues.
--
Sincerely,
Stephen R. van den
to actually fix/prevent
this problem, but for this to happen, the problem needs to become more
common first; and it doesn't look very likely that it will occur a lot.
--
Sincerely,
Stephen R. van den Berg.
Very funny, Mr. Scott. Now beam down my clothes!
).
That is already taken care of then. Git already does that accurately.
--
Sincerely,
Stephen R. van den Berg.
Very funny, Mr. Scott. Now beam down my clothes!
is f2542cf.
In *that* case, since the immediately preceding commit didn't contain
the file anymore (you deleted it a few commits ago), it doesn't know
where to get the history.
--
Sincerely,
Stephen R. van den Berg.
Very funny, Mr. Scott. Now beam down my clothes!
in the wild (by any git user), in the past
two years or so, AFAIK.
--
Sincerely,
Stephen R. van den Berg.
There are 10 types of people in the world.
Those who understand binary and those who do not.
)
{
--
1.5.6.15.gd06b4
--
Sincerely,
Stephen R. van den Berg.
There are 10 types of people in the world.
Those who understand binary and those who do not.
Stephen R. van den Berg wrote:
This is the patch in question, it is simple, reduces latency *a lot*
(and improves pgsql.pike performance by a factor of 2 or so; I could
imagine the boost is similar in other I/O-type of applications):
I have to correct myself. Apparently my refactoring
.
--
Sincerely,
Stephen R. van den Berg.
There are 10 types of people in the world.
Those who understand binary and those who do not.
. van den Berg.
Even if man could understand women, he still wouldn't believe it.
returning?
First I thought, they should not leave anything. Then I found some
sample code in the Shuffler which explicitly does a push_int(0) at the
end of a void function, so I copied that. Which is it now?
--
Sincerely,
Stephen R. van den Berg.
Even if man could understand women, he
,
Stephen R. van den Berg.
Even if man could understand women, he still wouldn't believe it.
the latest change.
What is the repository URL? I'd like to try this a little myself.
git clone git://git.cuci.nl/pike
to get started, the repository trails pikefarm by an hour or so at most.
--
Sincerely,
Stephen R. van den Berg.
Even if man could understand women, he still wouldn't
.
Personally I have used gitk a lot, but not specifically for
blame/annotation traversal, maybe it supports it though. Sorry, can't offer
more specific pointers here currently.
--
Sincerely,
Stephen R. van den Berg.
Even if man could understand women, he still wouldn't believe it.
saying how many
values it left on the stack, zero or more. That'd allow implementing
multiple return values.)
Why not change this (for 7.9) to avoid all this sillyness and indeed
support multiple return values?
--
Sincerely,
Stephen R. van den Berg.
Even if man could understand women, he
/math.c
--
Sincerely,
Stephen R. van den Berg.
Even if man could understand women, he still wouldn't believe it.
of inserting synthetic commits for the splits?
I.e. it's not clear to me if it solves anything.
--
Sincerely,
Stephen R. van den Berg.
Even if man could understand women, he still wouldn't believe it.
repo; since it contains the majority of the backports as merges.
Nevertheless, the git://git.cuci.nl/pike repository contains a lot of
backports and all branches in full correctly.
--
Sincerely,
Stephen R. van den Berg.
Even if man could understand women, he still wouldn't believe it.
, and doesn't have a lot of realworld implications.
--
Sincerely,
Stephen R. van den Berg.
Even if man could understand women, he still wouldn't believe it.
will contain lib/modules/String.pmod, but 7.3 will contain
lib/modules/_String.pmod instead).
I see. Well, I'll look into that, if I find differences, I'll create
fake splitcommits.
--
Sincerely,
Stephen R. van den Berg.
Even if man could understand women, he still wouldn't believe it.
the latest version of
git is in ubuntu.
In debian it's in testing.
Or, use: git clone git://git.kernel.org/pub/scm/git/git.git
and make install
it from the master branch.
--
Sincerely,
Stephen R. van den Berg.
Even if man could understand women, he still wouldn't believe it.
(graphics
mostly), and all files which have CR/LF endings because they were
created or intended for DOS/Windows.
Especially the graphics files (png/gif) were a PITA to correct.
--
Sincerely,
Stephen R. van den Berg.
Even if man could understand women, he still wouldn't believe it.
, wait or
compile from source (it's relatively painless).
--
Sincerely,
Stephen R. van den Berg.
Even if man could understand women, he still wouldn't believe it.
).
--
Sincerely,
Stephen R. van den Berg.
Even if man could understand women, he still wouldn't believe it.
intended for the Windows compiler, if I recall correctly; one
config/definition file (also in the Windows region), I forgot which exactly.
--
Sincerely,
Stephen R. van den Berg.
Even if man could understand women, he still wouldn't believe it.
,
Stephen R. van den Berg.
Even if man could understand women, he still wouldn't believe it.
,
when I latched onto git.
--
Sincerely,
Stephen R. van den Berg.
Even if man could understand women, he still wouldn't believe it.
, at some point in the future, repeat
steps f through h to get the fixes in.
I've personally exercised all these steps myself in the past few months,
several times, so did Martin, in order to keep up with my fixes.
It's not difficult to do.
--
Sincerely,
Stephen R. van den Berg.
Even
to actually fix that with a small price to pay:
anyone who already synced from that branch, will have to rebase, but
other than that, there is no downtime, no complicated dump-editing; it's
all less-filling and easy to use.
--
Sincerely,
Stephen R. van den Berg.
People who think they know
packages out there (some rough, some
polished) that give you more traditional interfaces to git.
In any case, if you want to appreciate the day-to-day capabilities of
git, you should learn what the index/staging area means and how it
works.
--
Sincerely,
Stephen R. van den Berg.
People who
never vote for myself, BTW).
--
Sincerely,
Stephen R. van den Berg.
People who think they know everything are annoying to those of us who do.
are increasingly non-developers. I.e. the growth rate of Debian
installs is higher than the growth rate of the number of developers
amongst them. This would be expected, not everyone has a need to use
VCS systems.
--
Sincerely,
Stephen R. van den Berg.
People who think they know
. (Didn't they change so that it always asks during
installation now, instead of you having to enable it manually?)
I think yes. But I rarely perform raw installations these days, I
simply copy a similar system, and then remove/add packages to taste.
--
Sincerely,
Stephen R. van den
at the page that lists the git projects, and most of the
core GNU tools I still remember from long ago were on it.
Look here to see what they moved to git:
http://git.savannah.gnu.org/gitweb/
--
Sincerely,
Stephen R. van den Berg.
People who think they know everything
continuing to use CVS. The point
just is that Git does everything SVN does already, but adds more at no
additional cost. So why settle for less?
--
Sincerely,
Stephen R. van den Berg.
People who think they know everything are annoying to those of us who do.
,
Stephen R. van den Berg.
People who think they know everything are annoying to those of us who do.
://plasmasturm.org/log/487/
--
Sincerely,
Stephen R. van den Berg.
People who think they know everything are annoying to those of us who do.
-svn. Git-svn is *very* good at restarting and picking up
right where it left off.
--
Sincerely,
Stephen R. van den Berg.
People who think they know everything are annoying to those of us who do.
a .gitattributes file
which can be put in every subdir(tree) you'd like).
You can actually chose to have them version controlled or not, i.e. they
can go into .git/info/attributes or they can go into .gitattributes
files that are placed inside the repository.
--
Sincerely,
Stephen R. van
the
repository. The only problem would be people that already commited new
commits on top of your commit, those commits get new hashes and need to
be rebased.
--
Sincerely,
Stephen R. van den Berg.
People who think they know everything are annoying to those of us who do.
the
dumpfile, or use SVK to mirror the SVN repo, then run git-svn.
--
Sincerely,
Stephen R. van den Berg.
How many weeks are there in a lightyear?
IPs).
- We're not expiring hostname_cache entries anywhere, it seems.
How is this supposed to work?
--
Sincerely,
Stephen R. van den Berg.
How many weeks are there in a lightyear?
.
If that is what this is about, then your patch is fine; if it is not,
I'd even advise against having an extra DNS-cache layer (at least as
long as it doesn't take the TTL into account).
--
Sincerely,
Stephen R. van den Berg.
How many weeks are there in a lightyear?
Stephen R. van den Berg wrote:
Stephen R. van den Berg wrote:
Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) @ Pike (-) developers forum wrote:
There should be a similar difference between
That should have read:
git blame README-CVS
git blame --find-copies-harder README-CVS
It turns out that git
as suggested earlier.
Using the merely braced version introduces other problems (sometimes).
--
Sincerely,
Stephen R. van den Berg.
There are three types of people in this world: those who make things happen,
those who watch things happen and those who wonder what happened.
?
--
Sincerely,
Stephen R. van den Berg.
The ultimate Darwin Award winner:
Going first in a Russian roulette game with a normal gun (no revolver).
.
--
Sincerely,
Stephen R. van den Berg.
Tomorrow will be cancelled due to lack of interest.
repository up to a state which can compete with SVN on almost
all levels. Give me 24 hours :-).
--
Sincerely,
Stephen R. van den Berg.
Beware: In C++, your friends can see your privates!
development because all tools need to be
adjusted to the new repository before we can proceed.
So, in the spirit of Leisure Suit Larry: split early, split often.
--
Sincerely,
Stephen R. van den Berg.
Beware: In C++, your friends can see your privates!
1 - 100 of 710 matches
Mail list logo
