From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: emacs-devel@gnu.org, perry@piermont.com
Subject: Re: minor bzr->git changes missed
Date: Thu, 13 Nov 2014 20:01:30 +0200 [thread overview]
Message-ID: <83tx23j7yd.fsf@gnu.org> (raw)
In-Reply-To: <5464F0B5.6010304@cs.ucla.edu>
> Date: Thu, 13 Nov 2014 09:56:05 -0800
> From: Paul Eggert <eggert@cs.ucla.edu>
> CC: perry@piermont.com, emacs-devel@gnu.org
>
> On 11/13/2014 09:36 AM, Eli Zaretskii wrote:
> > But why on master? All the changes of this kind should go to
> > the branch.
>
> Since those changes didn't fix any bugs, I assumed they weren't needed
> in the emacs-24 branch. It's possible that our definitions of "bug" differ.
No, our definitions don't differ in this case. But a change in a
documentation file or in .gitignore cannot possibly do any harm to the
stability of the release branch, and the fact that we switched to Git
is true for the branch as well. So leaving references to bzr on the
branch sounds wrong to me, even if it is not a bug in the literal
sense.
next prev parent reply other threads:[~2014-11-13 18:01 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
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 [this message]
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=83tx23j7yd.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=perry@piermont.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 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.