Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • G glib-networking
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 42
    • Issues 42
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 4
    • Merge requests 4
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GNOME
  • glib-networking
  • Repository

Switch branch/tag
  • glib-networking
  • proxy
  • gnome
  • gproxyresolvergnome.c
Find file BlameHistoryPermalink
  • David Zeuthen's avatar
    gnome-proxy: use lock to protect settings · fe23802c
    David Zeuthen authored May 18, 2011 and Dan Winship's avatar Dan Winship committed May 23, 2011
    Since it's fine for multiple threads to be calling into our module at
    the same time, we need to protect shared data, like the settings, with
    a lock. The problem was identified in bug 650439. This patch fixes the
    problem.
    
    https://bugzilla.gnome.org/show_bug.cgi?id=650439
    
    Signed-off-by: default avatarDavid Zeuthen <davidz@redhat.com>
    fe23802c

Replace gproxyresolvergnome.c

Attach a file by drag & drop or click to upload


Cancel
GitLab will create a branch in your fork and start a merge request.