From: "Perry E. Metzger" <perry@piermont.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Paul Eggert <eggert@cs.ucla.edu>, emacs-devel@gnu.org
Subject: Re: minor bzr->git changes missed
Date: Thu, 13 Nov 2014 12:44:05 -0500 [thread overview]
Message-ID: <20141113124405.7621c9af@jabberwock.cb.piermont.com> (raw)
In-Reply-To: <83y4rfj94o.fsf@gnu.org>
On Thu, 13 Nov 2014 19:36:07 +0200 Eli Zaretskii <eliz@gnu.org> wrote:
> Thanks. But why on master? All the changes of this kind should go
> to the branch.
For reference, is there a description of the full development
process, updated for the git world, one can read? I was under the
impression that people tracking development were supposed to be
operating off of master and that the 24 branch was only for bug fixes
to 24 -- that 25 would eventually be branched off of master in other
words. Clearly this is not the correct impression...
--
Perry E. Metzger perry@piermont.com
next prev parent reply other threads:[~2014-11-13 17:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-13 16:00 minor bzr->git changes missed Perry E. Metzger
2014-11-13 16:21 ` Eli Zaretskii
2014-11-13 16:37 ` Perry E. Metzger
2014-11-13 17:16 ` Eli Zaretskii
2014-11-13 17:18 ` Paul Eggert
2014-11-13 17:36 ` Eli Zaretskii
2014-11-13 17:44 ` Perry E. Metzger [this message]
2014-11-13 18:08 ` Eli Zaretskii
2014-11-13 18:14 ` Perry E. Metzger
2014-11-13 18:37 ` Eli Zaretskii
2014-11-13 19:11 ` Perry E. Metzger
2014-11-13 19:20 ` Eli Zaretskii
2014-11-13 21:54 ` Lars Magne Ingebrigtsen
2014-11-14 5:42 ` Eli Zaretskii
2014-11-14 7:10 ` Achim Gratz
2014-11-14 7:36 ` H. Dieter Wilhelm
2014-11-13 17:56 ` Paul Eggert
2014-11-13 18:01 ` Eli Zaretskii
2014-11-13 20:40 ` Paul Eggert
2014-11-14 5:20 ` Eli Zaretskii
2014-11-13 17:40 ` Perry E. Metzger
2014-11-13 17:36 ` Eric S. Raymond
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=20141113124405.7621c9af@jabberwock.cb.piermont.com \
--to=perry@piermont.com \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.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.
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.