Patch |
patch
|
2017-09-06 11:26:15 UTC |
2.94 KB |
no flags
|
Details |
cmake part of patch (updated) |
patch
|
2017-09-06 15:10:14 UTC |
3.26 KB |
no flags
|
Details |
patch (autotools part) |
text/plain
|
2017-09-06 15:13:06 UTC |
1.17 KB |
no flags
|
Details |
autotools part (update) |
patch
|
2017-09-08 10:52:11 UTC |
1.10 KB |
no flags
|
Details |
autotools patch (update 2) |
patch
|
2017-09-09 00:12:51 UTC |
2.07 KB |
no flags
|
Details |
Add Windows manifest to dbus-update-activation-environment.exe |
patch
|
2017-09-22 20:20:38 UTC |
4.48 KB |
no flags
|
Details |
Avoid dbus-update-activation-environment being catched by UAC |
patch
|
2017-09-26 10:34:57 UTC |
2.81 KB |
no flags
|
Details |
Avoid dbus-update-activation-environment being catched by UAC |
patch
|
2017-09-26 10:46:31 UTC |
2.81 KB |
no flags
|
Details |
Add Windows manifest to dbus-update-activation-environment.exe |
patch
|
2017-09-26 11:01:22 UTC |
2.99 KB |
no flags
|
Details |
Add Windows manifest to dbus-update-activation-environment.exe |
patch
|
2017-09-26 11:43:49 UTC |
3.24 KB |
no flags
|
Details |
Add Windows manifest to dbus-update-activation-environment.exe |
patch
|
2017-09-26 12:28:17 UTC |
3.22 KB |
no flags
|
Details |
Fix one remaining case not adding disable-uac.o to target dbus_update_activation_environment |
patch
|
2017-09-27 23:02:59 UTC |
798 bytes |
no flags
|
Details |
configure.log |
text/x-log
|
2017-10-04 13:52:05 UTC |
28.95 KB |
no flags
|
Details |
make.log |
text/x-log
|
2017-10-04 13:54:42 UTC |
1.86 MB |
no flags
|
Details |
Do not add custom UAC related manifest to cmake builds for MSVC on Windows |
patch
|
2017-10-18 06:27:47 UTC |
1.15 KB |
no flags
|
Details |
Do not add custom UAC related manifest to cmake builds for MSVC on Windows |
patch
|
2017-10-19 18:45:57 UTC |
1.31 KB |
no flags
|
Details |
Do not add custom UAC related manifest to cmake builds for MSVC on Windows |
patch
|
2017-10-21 09:38:55 UTC |
1.20 KB |
no flags
|
Details |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.