| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
regardless of sign/unsign differences. In other words, even though C
treats char literals as ints, if the rvalue is a literal inside single
quotes, and the lvalue is any kind of char, then assume the programmer
knows what he is doing.
|
|
gmon header. Idea from Alexey Dobriyan
|
|
|
|
it was only done partially and as a bonus, completely wrong.
seriously guys what was up with that?
|
|
with the initial commit but is required for a portable approach.
- make the tunnel id u_int and platform friendly, use predefined types.
- support configuration of layer 2 (ethernet) or layer 3
(point-to-point, default) modes. configuration is done using the
Tunnel (yes|point-to-point|ethernet|no) option is ssh_config(5) and
restricted by the PermitTunnel (yes|point-to-point|ethernet|no) option
in sshd_config(5).
ok djm@, man page bits by jmc@
|
|
|
|
ok reyk
|
|
|
|
ok jmc@
|
|
And strptime(3) %b and %B conversions are the same, so don't bother
trying both.
ok otto@
|
|
|
|
- add args to -w
- kill trailing whitespace
|
|
|
|
|
|
|
|
to not only consume, but also make sense of gcc __attribute__ syntax.
|
|
OpenSSH with OpenBSD.
Please note that tunnel forwarding is still somewhat experimental and
specific to the OpenBSD version of OpenSSH. Nevertheless, porting and
interoperability is possible due to the availability of a tun(4)-like
device for most of the other operating systems.
ok jmc@, requested by djm@
|
|
initial channel code bits by markus@. This is a simple and easy way to
use OpenSSH for ad hoc virtual private network connections, e.g.
administrative tunnels or secure wireless access. It's based on a new
ssh channel and works similar to the existing TCP forwarding support,
except that it depends on the tun(4) network interface on both ends of
the connection for layer 2 or layer 3 tunneling. This diff also adds
support for LocalCommand in the ssh(1) client.
ok djm@, markus@, jmc@ (manpages), tested and discussed with others
|
|
abbreviated month name.
ok jmc@ tedu@
|
|
|
|
- improve lists
- improve EXAMPLES
|
|
from daniel matic;
|
|
|
|
because -CC is something that showed up in a later gcc.
This is what happens when a pair of developers do not test on all
our architectures.
|
|
|
|
|
|
|
|
|
|
the user to tune his bktr(4) card with radioctl(4).
Also add a -v option prints out the available choices of channel
sets.
ok mickey@
|
|
|
|
|
|
ok brad, hints from jmc
|
|
that never got used in the first place;
|
|
"go ahead" and "nuke them" niallo@, xsa@
|
|
request, to make sure we are compatible with gnu;
|
|
|
|
- sync checkin_usage() with reality
|
|
|
|
|
|
If you 'vi file.c' and change stuff, then 'make depend && make' you'll
have a file.o file most definately more recent than the latest committed
version of file.c.
Then, if you rm file.c, and cvs update file.c, if 'file.c' is set to the
timestamp of the last committed version, a subsequent 'make' will not
rebuild the .o file.
to fix this we simply use the current timestamp when updating files.
thanks todd@!
|
|
now, when you checkout a tree with gnu cvs, opencvs no longer sees all
the files as modified, and visa versa.
this actually makes gnu cvs and opencvs dance together in working copies.
|
|
it it exists in the CVS admin dir.
- when writing the Entries file write it to Entries.Backup first and
then rename it to Entries when the writing was successfull.
|
|
|
|
|
|
|
|
|
|
|
|
- checkout in local mode (example: /cvs)
- update in local and server mode (example: /cvs and user@host:/cvs)
- import in local and server mode (example: /cvs and user@host:/cvs)
what remains to be done:
- not all options are supported yet, and update cannot pick up newly
added files yet. these things are pending and will be commited
real soon.
- checkout only works locally right now.
- fix rcs parsing code so that we don't fucking hog 100% cpu
on really BIG BIG BIG ass trees.
mainly tested by pedro@ and myself, thanks a lot pedro!
"go for it" niallo@
|
