- Dec 27, 2012
-
-
Balázs Úr authored
-
- Aug 17, 2010
-
-
Jorge González authored
-
- Aug 02, 2010
-
-
Frederic Peters authored
Quoting its NEWS file: "The m4sh macros AS_IF and AS_CASE can now be used in shell lists. The responsibility for supplying a trailing newline now belongs to the call site, but since most users did not add dnl, this generally results in fewer empty lines in configure." http://bugzilla.gnome.org/show_bug.cgi?id=591840
-
- Mar 22, 2010
-
-
Inaki Larranaga Murgoitio authored
-
- Sep 23, 2009
-
-
Josselin Mouette authored
This fixes monitoring failing to work when glib is built on a 2.6.27+ kernel but run on an older one. http://bugs.debian.org/544354 https://bugzilla.gnome.org/show_bug.cgi?id=593775
-
- Sep 03, 2009
-
-
Benjamin Otte authored
When doing a g_file_copy() with nofollow-symlinks (to copy a link for example), the later copying of the file attributes copies the source links 777 attributes to the target's attributes. As chmod affects the symlink target, this would cause such copies to always set the target to 777 mode. This patch makes setting the mode with nofollow-symlinks fail with NOT_SUPPORTED. The aforementioned g_file_copy() will still succeed, because it ignores errors of the attribute copy. This patch includes the whole patchset from master: 3826963e bb7852e3 48e0af01 e695c093
-
- Aug 29, 2009
-
-
Matthias Clasen authored
-
Matthias Clasen authored
-
- Aug 28, 2009
-
-
Matthias Clasen authored
-
Matthias Clasen authored
Bug 591995
-
Matthias Clasen authored
To avoid wasting entropy. Bug 593232.
-
When using errno in g_set_error with _(), preserve errno. Bug #592457.
-
This means we don't sync in the case where we created an (empty) temp file and now replace it with the data. This fixes (among other things) the performance of trashing files.
-
Matthias Clasen authored
-
Matthias Clasen authored
-
- Aug 24, 2009
-
-
Carles Ferrando authored
-
- Aug 14, 2009
-
-
Shixin Zeng authored
Patch from bug #591532.
-
Tor Lillqvist authored
Avoid "function declaration isn't a prototype" warnings from gcc 4.4 in the Windows-specific code.
-
- Aug 10, 2009
-
-
Antón Méixome authored
-
- Jun 27, 2009
-
-
Matthias Clasen authored
-
Matthias Clasen authored
-
Matthias Clasen authored
-
Matthias Clasen authored
-
g_filename_complete_get_completions() return value is meant to be a g_strfreev-compatible array i.e. NULL-terminated. However, pointer arrays aren't automagically NULL-terminated. This fixes bug 586868
-
- Jun 23, 2009
-
-
Matthias Clasen authored
This avoids a small window for races between pipe and fdset. Reported in bug 579933 by Thiago Macieira.
-
If G_FILE_MONITOR_WATCH_MOUNTS isn't specified, don't do all the work when the mtab changes.
-
Matthias Clasen authored
This oversight was pointed out in bug 585520.
-
Matthias Clasen authored
This fixes bug 585726.
-
Matthias Clasen authored
Turns out both the setter and the getter were broken... Fixes bug 585676.
-
Matthias Clasen authored
-
Matthias Clasen authored
To avoid leaking the inotify fd. Fixes bug 585478.
-
gets rid of compiler warnings
-
Matthias Clasen authored
We don't want to unset DISPLAY etc, if none is specified in the app launch context.
-
Matthias Clasen authored
Contrary to what the documentation says, g_string_chunk_insert_len was stopping at the first nul. Also add a test. Fixes bug 585088.
-
Matthias Clasen authored
And remove a bunch of grotty code to manipulate an environment array at the same time. Instead, simply call setenv in the child_setup function.
-
Matthias Clasen authored
-
The default implementation of g_file_copy() checked the size of the file to copy to give useful progress updates unconditionally. This can cause long delays on 1-connection FTP servers while it tries to open a second connection before it returns EBUSY. This patch makes this query only happen when we actually send progress updates.
-
Alexander Larsson authored
File attribute namespaces are delimited with "::", but build_attribute_list_for_copy only used ":", so we didn't copy any writable namespaces.
-
- Jun 18, 2009
-
-
Alexander Larsson authored
I'm not sure why we used the elaborate formula to convert the io-priority to the priority of the mainloop idle when emulating async i/o with idles. However, it causes the default io priority to be less than the normal idle prio, so the i/o won't be scheduled if there is an idle outstanding. There is really no great mapping to use here, doing blocking i/o in an idle of any prio is generally bad and apps doing a lot of async i/o should initialize threads. However, if we use the io-priority directly we at least avoid the starvation problem above and make things easier to understand.
-
A S Alam authored
-