Skip Menu |

This queue is for tickets about the BerkeleyDB CPAN distribution.

Report information
The Basics
Id: 42243
Status: resolved
Priority: 0/
Queue: BerkeleyDB

People
Owner: Nobody in particular
Requestors: nothingmuch [...] woobling.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: Several doc patches
Date: Fri, 9 Jan 2009 02:44:01 +0200
To: bug-BerkeleyDB [...] rt.cpan.org
From: "Yuval Kogman" <nothingmuch [...] woobling.org>

Message body is not shown because sender requested not to inline it.

Message body is not shown because sender requested not to inline it.

Message body is not shown because sender requested not to inline it.

Message body is not shown because sender requested not to inline it.

Hi Paul, Attached are several doc patches against BerkeleyDB 0.36 BTW, do you have any version control I could work with? I've been creating a repo each time I want to work on the module.
Subject: RE: [rt.cpan.org #42243] Several doc patches
Date: Mon, 12 Jan 2009 19:01:03 -0000
To: <bug-BerkeleyDB [...] rt.cpan.org>
From: "Paul Marquess" <Paul.Marquess [...] ntlworld.com>
Hi Thanks for the documentation patches. Will merge into my development copies. Sorry, no, I don't have a version control system available that you can interface to. Paul Show quoted text
> -----Original Message----- > From: nothingmuch@woobling.org via RT [mailto:bug-BerkeleyDB@rt.cpan.org] > Sent: 09 January 2009 00:44 > To: undisclosed-recipients: > Subject: [rt.cpan.org #42243] Several doc patches > > Thu Jan 08 19:44:17 2009: Request 42243 was acted upon. > Transaction: Ticket created by nothingmuch@woobling.org > Queue: BerkeleyDB > Subject: Several doc patches > Broken in: (no value) > Severity: (no value) > Owner: Nobody > Requestors: nothingmuch@woobling.org > Status: new > Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=42243 > > > > Hi Paul, > Attached are several doc patches against BerkeleyDB 0.36 > > BTW, do you have any version control I could work with? I've been creating a > repo each time I want to work on the module.