luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2025-01-22 20:26:17 +01:00
Code Issues Packages Projects Releases Wiki Activity

Typo fix.

Browse Source
This commit is contained in:
Matthias Clasen 2004-12-30 05:18:56 +00:00
parent b76a6afcb8
commit 647aba60aa
6 changed files with 22 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
ChangeLog
View File

@ -1,3 +1,7 @@
2004-12-30 Matthias Clasen <mclasen@redhat.com>
* glib/gfileutils.c (g_file_test): Typo fix.
2004-12-30 Tor Lillqvist <tml@iki.fi>
* glib/gutils.c (g_path_skip_root): Require UNC paths to start

4
ChangeLog.pre-2-10
View File

@ -1,3 +1,7 @@
2004-12-30 Matthias Clasen <mclasen@redhat.com>
* glib/gfileutils.c (g_file_test): Typo fix.
2004-12-30 Tor Lillqvist <tml@iki.fi>
* glib/gutils.c (g_path_skip_root): Require UNC paths to start

4
ChangeLog.pre-2-12
View File

@ -1,3 +1,7 @@
2004-12-30 Matthias Clasen <mclasen@redhat.com>
* glib/gfileutils.c (g_file_test): Typo fix.
2004-12-30 Tor Lillqvist <tml@iki.fi>
* glib/gutils.c (g_path_skip_root): Require UNC paths to start

4
ChangeLog.pre-2-6
View File

@ -1,3 +1,7 @@
2004-12-30 Matthias Clasen <mclasen@redhat.com>
* glib/gfileutils.c (g_file_test): Typo fix.
2004-12-30 Tor Lillqvist <tml@iki.fi>
* glib/gutils.c (g_path_skip_root): Require UNC paths to start

4
ChangeLog.pre-2-8
View File

@ -1,3 +1,7 @@
2004-12-30 Matthias Clasen <mclasen@redhat.com>
* glib/gfileutils.c (g_file_test): Typo fix.
2004-12-30 Tor Lillqvist <tml@iki.fi>
* glib/gutils.c (g_path_skip_root): Require UNC paths to start

4
glib/gfileutils.c
View File

@ -86,7 +86,7 @@
* %TRUE for %G_FILE_TEST_IS_SYMLINK and %FALSE for all other flags.
*
* You should never use g_file_test() to test whether it is safe
* to perform an operaton, because there is always the possibility
* to perform an operation, because there is always the possibility
* of the condition changing before you actually perform the operation.
* For example, you might think you could use %G_FILE_TEST_IS_SYMLINK
* to know whether it is is safe to write to a file without being
@ -104,7 +104,7 @@
* %G_FILE_TEST_IS_EXECUTABLE are implemented using the access()
* system call. This usually doesn't matter, but if your program
* is setuid or setgid it means that these tests will give you
* the answer for the real user ID and group ID , rather than the
* the answer for the real user ID and group ID, rather than the
* effective user ID and group ID.
*
* Return value: whether a test was %TRUE