sks-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Sks-devel] Re: [PATCH] Proper case handling for words index


From: Jason Harris
Subject: Re: [Sks-devel] Re: [PATCH] Proper case handling for words index
Date: Wed, 12 Aug 2009 12:48:54 -0400
User-agent: Mutt/1.5.19 (2009-01-05)

On Wed, Aug 12, 2009 at 12:54:43PM +0000, Kim Minh Kaplan wrote:

> This fixup script does not really deserve to be maintained.  Once the
> database is fixed its of no more use.  I hope we will quickly forget
> about it.

It is good OCaml sample code, at least.  I plan to keep it around in my
cloned repo.

> Nice.  By the way does removing Dbenv.RECOVER permit you to dump your db
> live, without stopping the sks server?

Definitely!

> I am very hesitant to fork SKS.  But as Yaron Minsky has been very quiet
> these last months it could be the only solution.  What do people think
> about this here?

Clearly, these patches are needed and should be made available in at
least in one public repo...

We should use the full power of mercurial for distributed development.
Most (all?) of the contributed patches added to SKS since switching to
hg are not attributed properly/fully via hg pulls, which is a shame.
Adding them to personal repos should be done first, and hg patchsets
published/emailed/pulled to track authorship.  Publishing plain old
patches and making everyone import/attribute them manually into their
own hg repo. is dumb.

To facilitate this, and to track patchset usage on various servers,
we need to at least add the hg changeset to the SKS version string.
The last official SKS is then known as address@hidden:46c6aaac31da, even
if it was pulled from your repo. and not Yaron's.

-- 
Jason Harris           |  NIC:  JH329, PGP:  This _is_ PGP-signed, isn't it?
address@hidden _|_ web:  http://keyserver.kjsl.com/~jharris/
          Got photons?   (TM), (C) 2004

Attachment: pgpWYVfTR1l2w.pgp
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]