public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Martin Galvan <martin.galvan@tallertechnologies.com>
To: Siddhesh Poyarekar <sid@reserved-bit.com>
Cc: libc-alpha@sourceware.org, "Carlos O'Donell" <carlos@redhat.com>,
	 Tom Tromey <tom@tromey.com>,
	Daniel Gutson <daniel.gutson@tallertechnologies.com>,
	 Roland McGrath <roland@hack.frob.com>
Subject: Re: [PATCH v5] Add pretty printers for the NPTL lock types
Date: Mon, 25 Apr 2016 21:59:00 -0000	[thread overview]
Message-ID: <CAOKbPbZd2Y9UDtOUDXX6YvWwOKmX9FQH7e1_bv_QgpDGUnhdTg@mail.gmail.com> (raw)
In-Reply-To: <CAOKbPba+=bD2L8jB2sUzgNEHDwKt+97-G-KCPaXZ6sN9EN4jaw@mail.gmail.com>

Pinging this again. A question before I send v6: Roland mentioned
$(py-const) shouldn't be part of before-compile since that's only for
stuff that must exist before C code can be compiled. However, if I
take it out the $(py-const) target won'r run. Where should I place it?

On Wed, Apr 20, 2016 at 9:43 AM, Martin Galvan
<martin.galvan@tallertechnologies.com> wrote:
> Pinging this again. If there's still no response in the following days
> I'll send a v6 with the same directory structure.
>
> On Mon, Apr 18, 2016 at 11:10 AM, Martin Galvan
> <martin.galvan@tallertechnologies.com> wrote:
>> Pinging this since there was no response.
>>
>> On Tue, Apr 12, 2016 at 6:27 PM, Martin Galvan
>> <martin.galvan@tallertechnologies.com> wrote:
>>> So far it appears to be working fine. I'll fix the other cosmetic
>>> issues and wait for Roland and Carlos' response before
>>> sending v6.
>
>
>
> --
>
>
> Martin Galvan
>
> Software Engineer
>
> Taller Technologies Argentina
>
>
> San Lorenzo 47, 3rd Floor, Office 5
>
> Córdoba, Argentina
>
> Phone: 54 351 4217888 / +54 351 4218211



-- 


Martin Galvan

Software Engineer

Taller Technologies Argentina


San Lorenzo 47, 3rd Floor, Office 5

Córdoba, Argentina

Phone: 54 351 4217888 / +54 351 4218211

      reply	other threads:[~2016-04-25 21:59 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-11 20:09 Martin Galvan
2016-04-11 20:38 ` Roland McGrath
2016-04-11 20:52   ` Martin Galvan
2016-04-11 21:31     ` Roland McGrath
2016-04-11 21:56       ` Martin Galvan
2016-04-11 22:17         ` Roland McGrath
2016-04-12  3:04           ` Siddhesh Poyarekar
2016-04-12  5:59             ` Siddhesh Poyarekar
2016-04-12 13:20               ` Martin Galvan
2016-04-12 14:55                 ` Martin Galvan
2016-04-12 15:59                   ` Siddhesh Poyarekar
2016-04-12 18:48                     ` Martin Galvan
2016-04-12 18:56                       ` Siddhesh Poyarekar
2016-04-12 19:05                         ` Martin Galvan
2016-04-12 21:28                           ` Martin Galvan
2016-04-18 14:10                             ` Martin Galvan
2016-04-20 12:44                               ` Martin Galvan
2016-04-25 21:59                                 ` Martin Galvan [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAOKbPbZd2Y9UDtOUDXX6YvWwOKmX9FQH7e1_bv_QgpDGUnhdTg@mail.gmail.com \
    --to=martin.galvan@tallertechnologies.com \
    --cc=carlos@redhat.com \
    --cc=daniel.gutson@tallertechnologies.com \
    --cc=libc-alpha@sourceware.org \
    --cc=roland@hack.frob.com \
    --cc=sid@reserved-bit.com \
    --cc=tom@tromey.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).