Martin Stjernholm, Roxen IS @ Pike developers forum wrote:
More precisely, -F is the relevant flag. Unfortunately it doesn't work
with -c. I've bug reported that. Still I think I'd prefer to configure
git status to not use the pager at all.
There were elaborate discussions about this on the git
Mirar @ Pike developers forum wrote:
Would it be possible for someone to sneak in this bugfix in Query.pike
at some stage?
+ return
+ hostname_cache[hostname] =
+( sizeof(hosts) hosts[random(sizeof( hosts ))] );
to make the hostname_cache in Protocols.HTTP.Session work as
...so, for a new Query object the hostname_cache will always be empty,
unless you supply it from some other direction before you start using
the query object. So this doesn't affect for instance
Protocols.HTTP.get_url et al, but it will affect
Protocols.HTTP.Session()-get_url.
It's probably a good idea to implement, yes. (But not for 7.8...?)
It works with supplying the query object with the mapping you are
using for the session. From HTTP/Session.pike:
q-hostname_cache=hostname_cache;
Mirar @ Pike developers forum wrote:
It's probably a good idea to implement, yes. (But not for 7.8...?)
It works with supplying the query object with the mapping you are
using for the session. From HTTP/Session.pike:
q-hostname_cache=hostname_cache;
For a session. Hrm. Well, let's put
Browsers are supposed to cache dns-ip util they are restarted.
http://christ1an.blogspot.com/2007/07/dns-pinning-explained.html
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
