[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gtk
Subject:    Re: Contribution to GLIB.
From:       Emmanuele Bassi <ebassi () gmail ! com>
Date:       2018-03-05 19:56:51
Message-ID: CALnHYQEcb7NDvKFQwn5Sz+uVoGFB6+8YPAVc8Z+y4VzYzU5oYw () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


Hi;

The current bug workflow is:

 - open a new issue in Bugzilla at:
https://bugzilla.gnome.org/enter_bug.cgi?product=glib
 - describe the issue with some detail
 - if you need to attach a patch, use a git formatted patch (git
format-patch) or, better yet, use git-bz

You can follow this page on the wiki:
https://wiki.gnome.org/Git/WorkingWithPatches

In the near future, it will be possible to use GitLab issues and merge
requests, but we are still in the process of migrating the bugs from one
platform to the other.

Ciao,
 Emmanuele.

On Tue, 6 Mar 2018 at 03:41, Elvis Teixeira <elvismtt@gmail.com> wrote:

> Hello guys,
>
> I have a suggestion, possibly a BUG-FIX, to GLIB. Can someone
> please point out the workflow for making such contribution. I saw that the
> GitHub repo is a read-only mirror so, I suppose there is another way.
> _______________________________________________
> gtk-list mailing list
> gtk-list@gnome.org
> https://mail.gnome.org/mailman/listinfo/gtk-list
>
-- 
https://www.bassi.io
[@] ebassi [@gmail.com]

[Attachment #5 (text/html)]

<div><div><div dir="auto">Hi;</div><div dir="auto"><br></div><div dir="auto">The \
current bug workflow is:</div><div dir="auto"><br></div><div dir="auto">  - open a \
new issue in Bugzilla at: <a \
href="https://bugzilla.gnome.org/enter_bug.cgi?product=glib">https://bugzilla.gnome.org/enter_bug.cgi?product=glib</a></div><div \
dir="auto">  - describe the issue with some detail</div><div dir="auto">  - if you \
need to attach a patch, use a git formatted patch (git format-patch) or, better yet, \
use git-bz  </div><div dir="auto"><br></div>You can follow this page on the wiki:  <a \
href="https://wiki.gnome.org/Git/WorkingWithPatches">https://wiki.gnome.org/Git/WorkingWithPatches</a></div><div \
dir="auto"><br></div><div dir="auto">In the near future, it will be possible to use \
GitLab issues and merge requests, but we are still in the process of migrating the \
bugs from one platform to the other.</div><div dir="auto"><br></div><div \
dir="auto">Ciao,</div><div dir="auto">  Emmanuele.</div><div dir="auto"><br><div \
class="gmail_quote" dir="auto"><div>On Tue, 6 Mar 2018 at 03:41, Elvis Teixeira \
&lt;<a href="mailto:elvismtt@gmail.com">elvismtt@gmail.com</a>&gt; \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div><div>Hello \
guys,<br><br></div>I have a suggestion, possibly a BUG-FIX, to GLIB. Can \
someone<br></div>please point out the workflow for making such contribution. I saw \
that the<br></div>GitHub repo is a read-only mirror so, I suppose there is another \
way.<br></div> _______________________________________________<br>
gtk-list mailing list<br>
<a href="mailto:gtk-list@gnome.org" target="_blank">gtk-list@gnome.org</a><br>
<a href="https://mail.gnome.org/mailman/listinfo/gtk-list" rel="noreferrer" \
target="_blank">https://mail.gnome.org/mailman/listinfo/gtk-list</a><br> \
</blockquote></div></div></div>-- <br><div dir="ltr" class="gmail_signature" \
data-smartmail="gmail_signature"><a href="https://www.bassi.io" \
target="_blank">https://www.bassi.io</a><br>[@] ebassi [@<a href="http://gmail.com" \
target="_blank">gmail.com</a>]</div>



_______________________________________________
gtk-list mailing list
gtk-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gtk-list


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic