From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Re: FEATURE: icalendar - link to original gnus message from org entry
Date: Fri, 27 Dec 2013 09:32:20 +0100 [thread overview]
Message-ID: <87mwjmhey3.fsf@dod.no> (raw)
In-Reply-To: <87sitf7yy4.fsf@building.gnus.org>
>>>>> Lars Ingebrigtsen <larsi@gnus.org>:
> Katsumi Yamaoka <yamaoka@jpl.org> writes:
>> As for me, a Gnus and Emacs merging engineer, it's ok that anyone
>> commits new features to the Gnus trunk. I'll keep them till the
>> Emacs feature freeze is lifted off.
> Great! Then we don't have to mess with different branches during the
> Emacs feature freeze.
Branches in git are really painless.
Especially when using something as simple as a branch made for
stabilization.
next prev parent reply other threads:[~2013-12-27 8:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-12 21:17 Jan Tatarik
2013-12-18 21:12 ` Adam Sjøgren
2013-12-19 20:12 ` Jan Tatarik
2013-12-26 15:51 ` Lars Ingebrigtsen
2013-12-26 22:10 ` Steinar Bang
2013-12-26 22:39 ` Katsumi Yamaoka
2013-12-27 3:30 ` Lars Ingebrigtsen
2013-12-27 8:32 ` Steinar Bang [this message]
2013-12-26 22:40 ` Jan Tatarik
2014-02-01 0:34 ` Lars Ingebrigtsen
2014-02-02 11:20 ` Jan Tatarik
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=87mwjmhey3.fsf@dod.no \
--to=sb@dod.no \
--cc=ding@gnus.org \
/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 NNTP newsgroup(s).