GNOME.org

2005-April Archive by Thread

Messages are ordered newest-to-oldest in this index. The newest threads will be at the top of this page, the oldest will be at the bottom.

Within a single thread, the first mail note is the START of the thread; the notes following that are in the chronological order of when they were received. So globally, newest messages are at the top, but within a thread, the oldest (the start of the thread) is at the top.

If you think about it, it is confusing. Just go with the flow and everything will be all right.

  • updated inotify., Robert Love
  • XChat plugin, Rich Midwinter
  • Beagle and Suse 9.3, Bodo Tasche
  • Is anyone using Fedora Core 3 ?, [NICK]
  • Did I get it wrong??, DANIEL hoggan
  • Can't install beagle under Suse 9.2, Maurizio Pozzobon
  • Dashboard integration into distributed enviroments, DANIEL hoggan
  • (no subject), DANIEL hoggan
  • beagled -- ioctl: Bad address, Thor Farrow
  • Beagle Compile Error, Alper KANAT
  • Beagle on Ubuntu Hoary, Martin Palma
  • Updated Fedora Rawhide Inotify Kernels, Ryan P Skadberg
  • configure.in & DBUS, MDK
  • Beagle 0.0.9, Jon Trowbridge
  • updatederest ever inotify kernels., Robert Love
  • gnomesharpglue & others not found, Shane Bishop
  • feature request - add mime type text/x-log, Andrew Replogle
  • Re: trigger the indexing of a specific directory without inotify, Nat Friedman
  • segfault.cam.novell.com update, David Barker
  • Re: beagle inotify ABI change, Miguel de Icaza
  • Hi, my name is Ubuntu. Can Beagle come out to play., Sami Haahtinen
  • upgrade mono on ubuntu, Shane Bishop
  • Beagle problem on Slackware 10.1, Charlie Law
    • Mail converted by MHonArc