From: Fejfighter <fejfighter@gmail.com>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: Vitaly Ankh <vitalyankh@gmail.com>, emacs-devel@gnu.org
Subject: Re: Merge feature/pgtk to master?
Date: Thu, 4 Nov 2021 22:30:13 +1100 [thread overview]
Message-ID: <CALohuRBtZBJn_x9YknAv8PxyrBcoL7fONAokE+c-wHhw30r=Pg@mail.gmail.com> (raw)
In-Reply-To: <CADwFkmmgShD2jjcDLT9M2iTQ2H3kVryZ5xO+GpFL_0KjTvJQqA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1168 bytes --]
Hi,
I did notice that the branch hasn't had a merge in from master since around
the time of the last discussion, aside from one patch.
There have been a couple of other issues mentioned outside of the bug
tracker, some I have patches that I haven't yet had a chance to push up,
and one or 2 others that I have been spinning on when I am stuck on other
emacs ideas.
I am happy to bring the pgtk branch up to par with master, for an easier
merge into master, and have created a savannah account(with this email) in
order to do that.
Sorry I missed this message at first,
Regards,
Jeff W
On Wed, Nov 3, 2021 at 2:13 AM Stefan Kangas <stefankangas@gmail.com> wrote:
> Vitaly Ankh <vitalyankh@gmail.com> writes:
>
> > Hi!
> >
> > I think the branch feature/pgtk is mature enough. I have used it for
> >
> > almost half a year and there are no bugs appearing now. Could we merge
> >
> > it to the master branch?
> >
> >
> > Regards,
> >
> > VitalyR
>
> I'm copying in Yuuki Harano and Jeff Walsh, who have been working on
> that branch.
>
> AFAICT, the latest discussion about this was here:
> https://lists.gnu.org/archive/html/emacs-devel/2021-08/msg00003.html
>
>
[-- Attachment #2: Type: text/html, Size: 1918 bytes --]
next prev parent reply other threads:[~2021-11-04 11:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-02 13:00 Merge feature/pgtk to master? Vitaly Ankh
2021-11-02 14:41 ` Stefan Kangas
2021-11-04 11:30 ` Fejfighter [this message]
2021-11-04 19:13 ` Jonathan Corbet
2021-11-04 20:12 ` Stefan Monnier
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='CALohuRBtZBJn_x9YknAv8PxyrBcoL7fONAokE+c-wHhw30r=Pg@mail.gmail.com' \
--to=fejfighter@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=stefankangas@gmail.com \
--cc=vitalyankh@gmail.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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.