From: Andreas Schwab <schwab@linux-m68k.org>
To: Paul Rankin <hello@paulwrankin.com>
Cc: Bastien Guerry <bzg@gnu.org>,
24073@debbugs.gnu.org, mail@nicolasgoaziou.fr,
npostavs@users.sourceforge.net
Subject: bug#24073: 25.1-rc2
Date: Sat, 01 Apr 2017 13:48:06 +0200 [thread overview]
Message-ID: <87shlspcw9.fsf@linux-m68k.org> (raw)
In-Reply-To: <1491041917.2348139.930696624.13E83F1A@webmail.messagingengine.com> (Paul Rankin's message of "Sat, 01 Apr 2017 20:18:37 +1000")
On Apr 01 2017, Paul Rankin <hello@paulwrankin.com> wrote:
> Emacs development appears to go along in a kind of unorthodox way. As someone familiar with git but unfamiliar with the Emacs dev workflow, my assumption was that anything in master is ready to ship out the door, with the bulk of commits happening on feature or hotfix branches. But it appears to work in the reverse, with everything going into master, and stable releases branching off, which seems like a good recipe for perpetual missing-of-boatsness. I remember when Emacs dev switched over to git there was a lot of confusion about how it works, so I think this is maybe the remnants of that.
It's not unusual that releases are created from a branch. A lot of
projects work like that.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2017-04-01 11:48 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-26 8:12 bug#24073: 24.5; outline-on-heading-p sees any invisible text property as outline inviisble Paul Rankin
2016-07-26 9:29 ` Paul Rankin
2016-07-26 15:14 ` Eli Zaretskii
2016-07-27 5:43 ` Paul Rankin
2016-07-28 4:25 ` bug#24073: 24.5; outline-on-heading-p sees any invisible text property as outline invisible Paul Rankin
2016-07-29 2:07 ` Noam Postavsky
2016-08-01 9:37 ` Paul Rankin
2016-08-01 14:16 ` npostavs
2016-08-02 3:27 ` Paul Rankin
2016-08-02 3:47 ` Noam Postavsky
2016-08-02 4:22 ` Paul Rankin
2016-08-02 14:27 ` Noam Postavsky
2016-08-02 7:20 ` Paul Rankin
2016-08-02 14:31 ` Noam Postavsky
2016-08-03 3:18 ` Paul Rankin
2016-08-31 1:12 ` bug#24073: 25.1-rc2 Paul Rankin
2016-08-31 2:41 ` Eli Zaretskii
2016-08-31 2:56 ` Paul Rankin
2016-08-31 8:59 ` John Wiegley
2016-08-31 9:12 ` Nicolas Petton
2016-08-31 14:25 ` Eli Zaretskii
2016-09-03 4:38 ` Paul Rankin
2016-09-18 14:39 ` Eli Zaretskii
2016-09-18 14:45 ` Nicolas Goaziou
2016-09-18 14:53 ` Eli Zaretskii
2016-09-19 9:40 ` Paul Rankin
2016-09-19 16:48 ` Eli Zaretskii
2016-09-20 5:37 ` Bastien Guerry
2016-09-30 8:06 ` Bastien Guerry
2017-03-30 8:18 ` Paul Rankin
2017-03-31 0:16 ` npostavs
2017-04-01 6:40 ` Paul Rankin
2017-04-01 7:20 ` Andreas Schwab
2017-04-01 8:06 ` Paul Rankin
2017-04-01 8:20 ` Andreas Schwab
2017-04-01 9:11 ` Paul Rankin
2017-04-01 9:37 ` Andreas Schwab
2017-04-01 10:18 ` Paul Rankin
2017-04-01 11:44 ` Eli Zaretskii
2017-04-01 12:05 ` Paul Rankin
2017-04-01 11:48 ` Andreas Schwab [this message]
2016-09-18 15:34 ` Bastien Guerry
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=87shlspcw9.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=24073@debbugs.gnu.org \
--cc=bzg@gnu.org \
--cc=hello@paulwrankin.com \
--cc=mail@nicolasgoaziou.fr \
--cc=npostavs@users.sourceforge.net \
/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).