From: Kaushal Modi <kaushal.modi@gmail.com>
To: "N. Raghavendra" <nyraghu27132@gmail.com>,
Emacs developers <emacs-devel@gnu.org>,
Eli Zaretskii <eliz@gnu.org>, John Wiegley <johnw@gnu.org>
Subject: Re: pdf-view removed from mailcap.el
Date: Sun, 17 Sep 2017 13:52:47 +0000 [thread overview]
Message-ID: <CAFyQvY1kXePxCP+EB17+=LRngwjf9Bo8890VQV8745HV74NpLg@mail.gmail.com> (raw)
In-Reply-To: <87fublxx6i.fsf@ailuros>
[-- Attachment #1: Type: text/plain, Size: 622 bytes --]
On Sun, Sep 17, 2017, 9:38 AM N. Raghavendra <nyraghu27132@gmail.com> wrote:
>
> Thanks for the quick action. The restoration is only in the emacs-26
> branch. Will the new change be incorporated into the master branch
> later? I ask this because I usually build Emacs from the master branch.
>
I often wonder that. Shouldn't each commit made to the stable branches be
merged to master at the same time?
I like that kind of flow in the Org repo. Notice how each time commits made
to maint (Org stable) branch are followed by merge commits to master: http
://orgmode.org/cgit.cgi/org-mode.git/log/
--
Kaushal Modi
[-- Attachment #2: Type: text/html, Size: 1271 bytes --]
next prev parent reply other threads:[~2017-09-17 13:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-17 10:37 pdf-view removed from mailcap.el N. Raghavendra
2017-09-17 12:30 ` Mark Oteiza
2017-09-17 13:38 ` N. Raghavendra
2017-09-17 13:49 ` Óscar Fuentes
2017-09-17 14:13 ` N. Raghavendra
2017-09-17 14:39 ` Eli Zaretskii
2017-09-17 14:41 ` N. Raghavendra
2017-09-17 16:55 ` Eli Zaretskii
2017-09-17 18:27 ` N. Raghavendra
2017-09-17 19:00 ` Eli Zaretskii
2017-09-17 13:52 ` Kaushal Modi [this message]
2017-09-17 14:37 ` Eli Zaretskii
2017-09-17 14:59 ` Kaushal Modi
2017-09-17 15:37 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAFyQvY1kXePxCP+EB17+=LRngwjf9Bo8890VQV8745HV74NpLg@mail.gmail.com' \
--to=kaushal.modi@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=johnw@gnu.org \
--cc=nyraghu27132@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).