| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This file has been touched 2 times in the last 7 years, and is no longer
up to date. Remove it to carry less unmaintained stuff around.
Also remove all references to it from file headers using
for file in `g grep -l 'See CREDITS for details about who has'`; do
sed -i '/See CREDITS for details about who has/,+1d' $file
done
as well as the different wording from rules/other/Toplevel.make.
Signed-off-by: Roland Hieber <rhi@pengutronix.de>
Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
|
| |
|
|
|
| |
Signed-off-by: Alexander Dahl <ada@thorsis.com>
Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
|
| |
|
|
| |
Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
|
|
|
libfaketime intercepts various system calls that programs use to
retrieve the current date and time. It then reports modified (faked)
dates and times (as specified by you, the user) to these programs.
This means you can modify the system time a program sees without
having to change the time system-wide.
libfaketime allows you to specify both absolute dates (e.g. 01/01/2004)
and relative dates (e.g., 10 days ago).
libfaketime might be used for various purposes, for example
- deterministic build processes
- debugging time-related issues, such as expired SSL certificates
- testing software for year-2038 compliance
libfaketime ships with a command line wrapper called "faketime" that
makes it easier to use, but does not expose all of libfaketime's
functionality. If your use case is not covered by the faketime command,
make sure to look in this documentation whether it can be achieved by
using libfaketime directly.
For more information, see https://github.com/wolfcw/libfaketime
Signed-off-by: Andreas Pretzsch <apr@cn-eng.de>
Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
|
