Re: minor bzr->git changes missed

[Eli Zaretskii <eliz@gnu.org>]

> Date: Thu, 13 Nov 2014 12:44:05 -0500
> From: "Perry E. Metzger" <perry@piermont.com>
> Cc: Paul Eggert <eggert@cs.ucla.edu>, emacs-devel@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?

Yes, admin/notes/repo and admin/notes/commits.

> 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...

The key issue here is "tracking development".  What exactly do you
mean by that, and how is that related to the issue at hand?

I wasn't talking to people who "track the development", I was talking
to contributors, whether actual or potential, to Emacs development and
maintenance.  Such contributors are expected, among other things, to
fix bugs when they see them, and bugs that exist on the release branch
should be fixed there (and later merged to master).

In this case, the leftover references to bzr are "bugs" on the branch
as well, because the next stable release will be made out of that
branch, and we don't want to disseminate incorrect information about
our repository.