From: Eli Zaretskii <eliz@gnu.org>
To: Karl Fogel <kfogel@red-bean.com>
Cc: emacs-devel@gnu.org
Subject: Re: Wrong commit message. What to do now?
Date: Wed, 14 Jul 2010 09:29:30 +0300 [thread overview]
Message-ID: <831vb6shit.fsf@gnu.org> (raw)
In-Reply-To: <8739vndo36.fsf@red-bean.com>
> From: Karl Fogel <kfogel@red-bean.com>
> Date: Tue, 13 Jul 2010 18:16:45 -0400
>
> Also, I had forgotten: are we not supposed to be committing to trunk
> right now?
Why not? There's no branch or feature freeze anywhere in sight.
> (Aside: it feels somewhat hard to be a drive-by maintainer these days,
> which is what I am. I try to be responsible about bookmark, saveplace,
> and mail-hist stuff, but I can't follow project status in depth. The
> fact that trunk sometimes is, and sometimes is not, the right place to
> push changes makes this role a bit more difficult. Not unworkably
> difficult, but it does lead to mistakes sometimes.)
If you commit a safe bugfix for a problem that exists in Emacs 23.2,
consider committing to the emacs-23 branch, not to the trunk; it will
get merged with the trunk later. And there's a request from Stefan
and Yidong to commit either to the trunk or to emacs-23, but not to
both. This is to make the merges from emacs-23 to the trunk a bit
less painful. That's all, there are no other rules. How's that too
complicated, I don't see.
next prev parent reply other threads:[~2010-07-14 6:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-13 22:16 Wrong commit message. What to do now? Karl Fogel
2010-07-13 22:43 ` Óscar Fuentes
2010-07-13 23:17 ` Karl Fogel
2010-07-13 23:33 ` Óscar Fuentes
[not found] ` <871vb6dhm7.fsf@red-bean.com>
2010-07-14 0:54 ` Óscar Fuentes
2010-07-26 22:49 ` Stefan Monnier
2010-07-14 3:23 ` Stephen J. Turnbull
2010-07-14 3:42 ` Karl Fogel
2010-07-14 6:29 ` Eli Zaretskii [this message]
2010-07-14 15:29 ` Karl Fogel
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=831vb6shit.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=kfogel@red-bean.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.