All of lore.kernel.org
 help / color / mirror / Atom feed
From: eamanu <eamanu@yaerobi.com>
To: Julia Lawall <julia.lawall@inria.fr>
Cc: cocci@systeme.lip6.fr
Subject: Re: [Cocci] coccinelle depends on unmaintained pygtk
Date: Tue, 4 Feb 2020 12:25:55 -0300	[thread overview]
Message-ID: <909d202d-9a8a-d010-107b-80c07febcb0f@yaerobi.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2002041556540.3345@hadrien>

Hi!

On 04/02/2020 11:59, Julia Lawall wrote:
> On Tue, 4 Feb 2020, eamanu wrote:
>
>> Hi everybody,
>>
>> Sorry if this issues is duplicated, I am new in the mailing list
>> and in a very quickly searching I didn't found about this issue.
>>
>> I am working on Coccinelle package on Debian
> Thanks!
>
>> and currently
>> exist the next bug [1].
>>
>> There is any plan to port to use GObject Instrospection?
>>
>> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885267
> I think we should just drop the code that depends on it.  It was added for
> a MS thesis more than 10 years ago, and I don't think anyone has used it
> since.
>
> I will look into it.

Great, if you need help, I can help :-)

I will wait for any news. Thanks

eamanu
>
> julia

_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci

  reply	other threads:[~2020-02-04 15:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-04 14:48 [Cocci] coccinelle depends on unmaintained pygtk eamanu
2020-02-04 14:59 ` Julia Lawall
2020-02-04 15:25   ` eamanu [this message]
2020-02-27  9:43     ` Nicolas Palix
2020-02-27  9:45       ` Julia Lawall
2020-02-27  9:56         ` Nicolas Palix
2020-02-27 10:04           ` Julia Lawall
2020-02-28 11:39             ` Emmanuel Arias
2020-02-28 12:45               ` Julia Lawall
2020-02-28 15:14                 ` eamanu

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=909d202d-9a8a-d010-107b-80c07febcb0f@yaerobi.com \
    --to=eamanu@yaerobi.com \
    --cc=cocci@systeme.lip6.fr \
    --cc=julia.lawall@inria.fr \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.