<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.comp.version-control.mercurial.general">
    <title>gmane.comp.version-control.mercurial.general</title>
    <link>http://blog.gmane.org/gmane.comp.version-control.mercurial.general</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10832"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10830"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10828"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10821"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10813"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10812"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10797"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10796"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10792"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10778"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10768"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10767"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10761"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10758"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10745"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10736"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10734"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10732"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10713"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10711"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10832">
    <title>Feature request: mark "dead ends"</title>
    <link>http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10832</link>
    <description>Hi again,

in one of my repositories I have checked in some changeset X for feature A 
which I could never made to work.  Later, I have restarted from X's parent and 
some dozens of revisions later I finished the same feature A in another way.
Now I have this extra head with the unfinished changes which I don't need 
anymore.

This extra head gets in my way when using "hgview" (it always appears at the 
very top, although it is very old).

AFAICS, I have three options:
1) Use a dummy merge to make the unnamed branch inactive.  That would look 
like I actually used code from my first try, which I did not.
2) Use strip/mq/convert etc. to remove this head from my repo.  I have no 
intention to do this.
3) Leave it as it is, and try to fix hgview for example.

I would like to have option 4) - mark the branch as inactive without merging 
it.  Apparently, this is not yet possible with hg, right?

What do you people think?  (I bet most people are content with opion 1, but 
what do you think about 4?)

Have a nice d</description>
    <dc:creator>Hans Meine</dc:creator>
    <dc:date>2008-12-01T14:52:56</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10830">
    <title>[PATCH] tests: allow cvs import to reorder its filename list</title>
    <link>http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10830</link>
    <description># HG changeset patch
# User Frank Kingswood &lt;frank&lt; at &gt;kingswood-consulting.co.uk&gt;
# Date 1228138924 0
# Node ID b1c1b4f98b74bfa32991d33bdb4a47215cdeb842
# Parent  79d1bb737c16b343e33be7cd7e22dcc4e7bfab0b
tests: allow cvs import to reorder its filename list
also fix script to generate non-zero length test file b.

diff -r 79d1bb737c16 -r b1c1b4f98b74 tests/test-convert-cvs-branch
--- a/tests/test-convert-cvs-branchMon Dec 01 14:20:20 2008 +0100
+++ b/tests/test-convert-cvs-branchMon Dec 01 13:42:04 2008 +0000
&lt; at &gt;&lt; at &gt; -28,8 +28,9 &lt; at &gt;&lt; at &gt;
 
 mkdir src
 cd src
-echo "1" &gt; a &gt; b
-cvscall import -m "init" src v0 r0
+echo "1" &gt; a
+echo "1" &gt; b
+cvscall import -m "init" src v0 r0 | sort
 cd ..
 cvscall co src
 cd src
diff -r 79d1bb737c16 -r b1c1b4f98b74 tests/test-convert-cvs-branch.out
--- a/tests/test-convert-cvs-branch.outMon Dec 01 14:20:20 2008 +0100
+++ b/tests/test-convert-cvs-branch.outMon Dec 01 13:42:04 2008 +0000
&lt; at &gt;&lt; at &gt; -1,10 +1,10 &lt; at &gt;&lt; at &gt;
 % create cvs repository
 % Create a new project
+
+
 N src/a
 N src/b
-
 No conflic</description>
    <dc:creator>Frank Kingswood</dc:creator>
    <dc:date>2008-12-01T14:24:18</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10828">
    <title>Please, some "partial-silency" option for pull</title>
    <link>http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10828</link>
    <description>
It would be nice if hg pull could be configured to suppress output
when there are no changes transferred.

Rationale:

   I frequently use different "pull many repositories at once"
   scripts, from

      for dir in *
      do
          hg --cwd $dir pull 
      done

   to more complicated "syncthemall" scripts.

   The output of such a command is difficult to read as truly useful
   information is lost among numerous

      pulling from (...)
      searching for changes
      no changes found

   messages. I'd prefer to see only info about directories where
   "something" happened.

   (at the same time hg -q pull supressess everything, also the
    useful info)

Syntax suggestion:

   hg pull --silent

Alternative syntax suggestion:

   It could be even better idea to introduce some global option of
   similar meaning (report "interesting" information but suppress
   notifications that nothing happened, nothing was found, no files
   were updated, nothing was added etc etc). This would establish a
   co</description>
    <dc:creator>Marcin Kasperski</dc:creator>
    <dc:date>2008-12-01T11:45:30</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10821">
    <title>qdiff output with commit message and user info</title>
    <link>http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10821</link>
    <description>Hi,

is there any way to include to hg qdiff output the commit message and
the user name recorded during qrefresh? Alternatively can I force to
include -p option to mq patches as stored under .hgrc/patches ?

Regards, Igor
</description>
    <dc:creator>Igor Bukanov</dc:creator>
    <dc:date>2008-11-30T21:37:44</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10813">
    <title>clone: source path can't contain '#'</title>
    <link>http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10813</link>
    <description>A user of TortoiseHg has reported this, which I confirmed with recent
crew version of Mercurial:

    $ hg -R crew# tip
    changeset:   6797:694223a29ad4
    tag:         tip
    user:        byron&lt; at &gt;base2.cc
    date:        Thu Jul 03 20:53:14 2008 -0700
    summary:     Added missing --config global option to zsh_completion.

    $ hg clone crew# c1
    abort: repository crew not found!
</description>
    <dc:creator>TK Soh</dc:creator>
    <dc:date>2008-11-30T02:50:46</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10812">
    <title>email.charsets trouble</title>
    <link>http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10812</link>
    <description>Hi everyone,

I recently had a chance to upgrade the Hg installation at hg.hellug.gr
to a crew snapshot.  One of the repositories hosted there is the common
`translation tree' of the Greek FreeBSD documentation team at:

    http://hg.hellug.gr/freebsd/doc-el/

With older versions of Hg we would get commit email notifications whose
included patches did not have a charset/encoding.  The rest of the email
was really encoded with email.charsets = iso-8859-7 though, so most
mailers would correctly infer that the patch was iso-8859-7 too.

With the recent Mercurial installation, patchbomb seems to be using
utf-8 as the email charset, no matter what I try to use in the
`.hg/hgrc' file of the relevant repository.

Most of the patches we commit in the Greek documentation are encoded in
iso-8859-7, so they show up as a long list of question marks in the
emails sent by patchbomb, i.e.:

% diff -r 913b74dbc96e -r 51e99cebb8bd el_GR.ISO8859-7/books/handbook/kernelconfig/chapter.sgml
% --- a/el_GR.ISO8859-7/books/handboo</description>
    <dc:creator>Giorgos Keramidas</dc:creator>
    <dc:date>2008-11-29T23:03:57</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10797">
    <title>Integrity problems on CIFS mounted file system</title>
    <link>http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10797</link>
    <description>
Running the following script on the local file system works fine.
But running it on a CIFS mounted file system causes integrity errors.

#!/bin/bash
hg init original
cd original
echo '' &gt; NotRenamed.txt
hg add
hg commit -m 'NotRenamed'
cd ..

hg clone original clone
cd clone
cp NotRenamed.txt Renamed.txt
hg remove NotRenamed.txt
hg add
hg commit -m 'Renamed'
hg push
hg verify

cd ../original
hg update
hg verify


Here is my fstab.
If anybody has any suggestions I would be most thankful.

//seabsrv01/dev$           /mnt/dev            cifs
uid=morgan,gid=morgan,credentials=/home/morgan/.smbcredentials,iocharset=utf8,dir_mode=0777,file_mode=0777
0 0
</description>
    <dc:creator>Seamor</dc:creator>
    <dc:date>2008-11-28T17:06:11</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10796">
    <title>LOC of different version control systems</title>
    <link>http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10796</link>
    <description>According to:

http://www.ohloh.net/projects/compare?metric=Codebase&amp;project_0=Mercurial&amp;project_1=Git&amp;project_2=Bazaar+Version+Control

Git, Bazaar and Mercurial have 350k, 150k and 50k lines of souce
code respectively.

Initially I made the above comparison between just Git and Mercurial and figured
it might be accounted for by the fact that Git is in C and Mercurial
is in Python
but then I added Bazaar and it is also written in Python.

Other possibilities might be how extensions are counted or just plain error in
measurement.

Does anyone understand the differences between these systems sufficiently
to explain these seemingly large differences?
</description>
    <dc:creator>Gabor Grothendieck</dc:creator>
    <dc:date>2008-11-28T18:06:27</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10792">
    <title>Merge commits do only show files changed during the merge as changed (i.e. those with conflicts or similar). Bug or feature?</title>
    <link>http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10792</link>
    <description>
First a few steps to reproduce the problem. Then the question is at the
end:

~/tmp$ hg init hgtest
~/tmp$ cd hgtest/
~/tmp/hgtest$ echo file1 &gt; file1.txt
~/tmp/hgtest$ echo file2 &gt; file2.txt
~/tmp/hgtest$ hg add .
adding file1.txt
adding file2.txt
~/tmp/hgtest$ hg ci -m "Initial checkin" 
~/tmp/hgtest$ ls &gt;&gt; file1.txt 
~/tmp/hgtest$ hg ci -m "Change in file1"
~/tmp/hgtest$ hg update 0
1 files updated, 0 files merged, 0 files removed, 0 files unresolved
~/tmp/hgtest$ ls &gt;&gt; file2.txt 
~/tmp/hgtest$ hg ci -m "Change in file2, create another head"
created new head
~/tmp/hgtest$ hg merge -r1
1 files updated, 0 files merged, 0 files removed, 0 files unresolved
(branch merge, don't forget to commit)
~/tmp/hgtest$ hg ci -m "Merge"
~/tmp/hgtest$ hg log -v -r3
changeset:   3:936aaa1c9975
tag:         tip
parent:      2:1dd8a64b18b0
parent:      1:741fd3bcb38d
user:        Jens Lund &lt;jens.lund&lt; at &gt;nordea.com&gt;
date:        Fri Nov 28 12:31:52 2008 +0100
description:
Merge

What puzzles we is that the merge commit (3) show</description>
    <dc:creator>jens.lund&lt; at &gt;nordea.com</dc:creator>
    <dc:date>2008-11-28T12:37:56</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10778">
    <title>Merging with Emacs and ediff-mode</title>
    <link>http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10778</link>
    <description>Hi everyone,

I've been using two script-wrappers for merging for a while now:

  hg-merge

        This one tries Mercurial's pre-merge, then diff3 and falls back
        to merging in an ${EDITOR} buffer with conflict markers.

  ediff-merge

        This one disables pre-merge, it tries diff3 but if that fails
        too it starts with a clean copy of $local and fires up Emacs in
        ediff-mode to do a 3-way merge.

The .hgrc options that enable these are:

  [merge-tools]
  ediff.priority = 0
  ediff.premerge = False
  ediff.binary = False
  ediff.gui = True
  ediff.executable = /home/keramida/bin/ediff-merge
  ediff.args = $local $base $other
  script.priority = 1
  script.premerge = True
  script.binary = False
  script.gui = False
  script.executable = /home/keramida/bin/hg-merge
  script.args = $local $base $other

and I have in my ~/bin directory the attached scripts.

Do these look ok as merge helpers for UNIX workstations?  Should I add
these to the Wiki?

</description>
    <dc:creator>Giorgos Keramidas</dc:creator>
    <dc:date>2008-11-28T04:24:28</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10768">
    <title>Setting Up HG To Work With Winmerge - Windows Cmd Line Use</title>
    <link>http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10768</link>
    <description>    Hello,


    I'm using Mercurial on Windows using the command line, and would 
like to ask how to set up merge to use the WinMerge utility.

    Specifically, the online documentation shows this for kdiff3:


&lt;quote&gt;

In Mercurial 1.0 you can add the following to .hgrc:

[merge-tools]
kdiff3.args = $base $local $other -o $output
&lt;/quote&gt;
and I'd like to ask what .hgrc configuration is necessary for this.

Many thanks!

Bye,

TD



</description>
    <dc:creator>The Dude</dc:creator>
    <dc:date>2008-11-27T07:37:24</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10767">
    <title>Bug report (hg qpush)</title>
    <link>http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10767</link>
    <description>Hi,

I got the message below when running
    hg qpush gfx_debugging_stuff_2008-11-25.diff
on a Mozilla repository. After this, the queue state looks like this
    $ hg qa
    0 U gfx_debugging_stuff_2008-11-25.diff
    1 A cairo-os2_fix_as_upstream.diff
    2 A bug453705_domquickstubs.diff
    3 A bug451278_nscom_workaround.diff
The files that the patch is supposed to touch were not changed. I worked
around this problem now by doing
    hg qpop -a
before trying the qpush again...

The messages don't look like a system specific problem, but this is with
Mercurial running on OS/2.

Cheers,
    Peter.

** report bug details to http://www.selenic.com/mercurial/bts
** or mercurial&lt; at &gt;selenic.com
** Mercurial Distributed SCM (version a490a0c59b94fef613ac87813e12b992421d0948)
Traceback (most recent call last):
   File "f:/Python/Scripts/hg", line 22, in ?
     mercurial.dispatch.run()
   File "f:/Python/lib/site-packages/mercurial/dispatch.py", line 20, in run
     sys.exit(dispatch(sys.argv[1:]))
   File "f:/Python/</description>
    <dc:creator>Peter Weilbacher</dc:creator>
    <dc:date>2008-11-27T07:29:54</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10761">
    <title>mercurial + nginx</title>
    <link>http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10761</link>
    <description/>
    <dc:creator>allnightlong</dc:creator>
    <dc:date>2008-11-26T23:40:27</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10758">
    <title>rebasing only a single changeset</title>
    <link>http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10758</link>
    <description>-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Mozilla is going to cut a long-lived release branch shortly. We will be
cherry-picking individual changes from the trunk to the release branch. I
originally thought that the rebase extension would be perfect for this task:

hg rebase -s revtocherrypick -t releasebranch

But I forgot that rebase will not rebase the single revision I'm interested
in: it will only rebase entire branches.

The transplant extension could be used for this, but doesn't do 3-way
merging (and the rebase extension is in general better designed). How hard
would it be to add "rebase a single revision" to the rebase extension?

- --BDS
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJLWriSSwGp5sTYNkRApc8AKDFSkO6OdFLtNVljy7iOQOYRY9xjgCeL8y0
o4zeG35ugDZneposLEYhTz8=
=JbZh
-----END PGP SIGNATURE-----
</description>
    <dc:creator>Benjamin Smedberg</dc:creator>
    <dc:date>2008-11-26T15:27:30</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10745">
    <title>Call for testing: mercurial 1.1</title>
    <link>http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10745</link>
    <description>Since the 1.1 release is approaching, it would be nice to have some additional
testing, preferably using crew repo:
http://hg.intevation.org/mercurial/crew

Thanks!

Benoit
</description>
    <dc:creator>Benoit Boissinot</dc:creator>
    <dc:date>2008-11-26T11:29:26</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10736">
    <title>tkdiff seems to need a new maintainer</title>
    <link>http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10736</link>
    <description>some time ago someone showed me the very nice graphical diff-tool called
tkdiff. The latest version that I got from sourceforce however doesn't
support hg. Still, someone already submitted a very complete patch for
hg in the bug-tracking system (http://tinyurl.com/5g3hjv)

But apparently nothing is happening with tkdiff anymore and the patch
was not applied yet. Today I found out that it was maintained by the
Debian QA-Group for some time, but it was orphaned and needs a new
maintainer (http://packages.qa.debian.org/t/tkdiff.html)

Maybe someone on this list happens to have an interest in becoming the
maintainer?

</description>
    <dc:creator>J.S. van Bethlehem</dc:creator>
    <dc:date>2008-11-25T12:37:11</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10734">
    <title>How to know file size at a given revision</title>
    <link>http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10734</link>
    <description>Hello,

I see most web styles offer repository files listing at arbitrary
revision with entry size. I'm interested into this information and
I would like to make hg output it from the CLI, for exemple using locate
with --template ... {size} ... or so.

But it seems that locate won't use --template, so I'm a bit stuck. I'm
still a bit lost with differences between hg web styles and CL
templates.

How would you recommand me to proceed please ?

Thanks

</description>
    <dc:creator>Paul R</dc:creator>
    <dc:date>2008-11-25T11:28:21</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10732">
    <title>hook script to get version info</title>
    <link>http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10732</link>
    <description>Hi,

is there a hook script which makes sure that something like "hg id"'s 
output can be fed into some file or process at clone time or after an 
update?

Marko
</description>
    <dc:creator>Marko Käning</dc:creator>
    <dc:date>2008-11-25T10:18:49</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10713">
    <title>passing username and password in non-interactive mode</title>
    <link>http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10713</link>
    <description/>
    <dc:creator>Bastian Doetsch</dc:creator>
    <dc:date>2008-11-24T18:09:38</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10711">
    <title>Moving from One Hg to Another</title>
    <link>http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10711</link>
    <description/>
    <dc:creator>Benjamin Johnson</dc:creator>
    <dc:date>2008-11-24T16:26:14</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10707">
    <title>hgweb and templating</title>
    <link>http://comments.gmane.org/gmane.comp.version-control.mercurial.general/10707</link>
    <description>Hi!

I've been trying to customize the look&amp;feel of my hgweb to match the
rest of the layout of my site, but I haven't been able to find a
reference of how to customize it.

Are there any reference documentation on how to write my own templates?
Is hgweb using any standard templating mechanism that I can look at?

--
Trygve
</description>
    <dc:creator>Trygve Laugstøl</dc:creator>
    <dc:date>2008-11-24T15:04:29</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.version-control.mercurial.general">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.version-control.mercurial.general</link>
  </textinput>
</rdf:RDF>
