On Mon, Sep 02, 2019 at 01:48:14PM -0400, Alvaro Herrera wrote:
> Agreed ... that's pretty much the same thing I tried to say upthread. I
> wrote my own synopsis, partly using your suggestions. I reworded the
> description for the routines (I don't think there's any I didn't touch),
> added a
On Tue, Jul 30, 2019 at 4:47 PM Michael Paquier wrote:
> On Fri, Jul 26, 2019 at 09:51:34AM -0400, Andrew Dunstan wrote:
> > I've fixed the bitrot and some other infelicities on this patch. It's
> > not commitable yet but I think it's more reviewable.
>
> Thanks, I had a look at this version.
>
>
On Fri, Jul 26, 2019 at 09:51:34AM -0400, Andrew Dunstan wrote:
> I've fixed the bitrot and some other infelicities on this patch. It's
> not commitable yet but I think it's more reviewable.
Thanks, I had a look at this version.
+ # Returns the real directory for a virtual path directory under
On 7/10/19 9:38 AM, Alvaro Herrera wrote:
> On 2019-Apr-11, Iwata, Aya wrote:
>
>> In the above document, why not write a description after the function name?
>> I think it is better to write the function name first and then the
>> description.
>> In your code;
>> #Checks if all the tests
On 2019-Apr-11, Iwata, Aya wrote:
> In the above document, why not write a description after the function name?
> I think it is better to write the function name first and then the
> description.
> In your code;
> #Checks if all the tests passed or not
> all_tests_passing()
>
> In my
On Tue, Jul 09, 2019 at 03:16:01PM +0200, Daniel Gustafsson wrote:
> The v2 patch is somewhat confused as it has Windows carriage returns rather
> than newlines, so it replaces the entire file making the diff hard to read.
> It
> also includes a copy of TestLib and the v1 patch and has a lot of
> On 7 Apr 2019, at 20:04, Ramanarayana wrote:
> Please find the updated patch. Added to the commitfest as well
The v2 patch is somewhat confused as it has Windows carriage returns rather
than newlines, so it replaces the entire file making the diff hard to read. It
also includes a copy of
Hi Ram,
I think this documentation helps people who want to understand functions.
>Please find the updated patch. Added to the commitfest as well
I have some comments.
I think some users who would like to know custom function check
src/test/perl/README at first.
How about add comments to the
Hi,
Please find the updated patch. Added to the commitfest as well
Regards,
Ram.
v2_perldoc_testlib.patch.patch
Description: Binary data
On Fri, Mar 22, 2019 at 04:59:58PM +0530, Ramanarayana wrote:
> Please find the first version of the patch for review. I was not sure what
> some of the functions are used for and marked them with TODO.
This is only adding some documentation to an internal perl module we
ship, so it is far from
Hi,
Please find the first version of the patch for review. I was not sure what
some of the functions are used for and marked them with TODO.
Cheers
Ram 4.0
v1_perldoc_testlib.patch
Description: Binary data
Sure, please go ahead.
Regards,
Prajwal.
On Thu, 21 Mar 2019, 19:11 Ramanarayana, wrote:
> Hi,
> Can I take this up?
>
> Regards,
> Ram
>
Hi,
Can I take this up?
Regards,
Ram
On Tue, Mar 19, 2019 at 09:05:29AM -0300, Alvaro Herrera wrote:
> Yes, it is, please do.
+1.
--
Michael
signature.asc
Description: PGP signature
On 2019-Mar-19, Prajwal A V wrote:
> I could not find the perldoc for TestLib module in src/test/perl and found
> some difficultly in understanding what each function does while other
> modules in the src/test folder had perldoc and it was easy to understand
> the functions.
>
> I would like to
Hi Hackers,
I was going through the regression testing framework used in postgres. I
was trying to understand the custom functions written in perl for postgres.
I could not find the perldoc for TestLib module in src/test/perl and found
some difficultly in understanding what each function does
16 matches
Mail list logo
