From: David Kastrup <dak@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: Committing to both branches
Date: Tue, 01 Jun 2010 10:33:02 +0200 [thread overview]
Message-ID: <876323b1a9.fsf@lola.goethe.zz> (raw)
In-Reply-To: AANLkTimnc5EE-K4dcr2VK8iEiIzG3isCE58hjeqVl83_@mail.gmail.com
Juanma Barranquero <lekktu@gmail.com> writes:
>> Can people *please* stop committing to both emacs-23 and trunk branches?
>
> Not even with "Backport from trunk" in the summary?
Independent commits will likely cause merge conflicts.
--
David Kastrup
next prev parent reply other threads:[~2010-06-01 8:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-01 2:28 Committing to both branches Stefan Monnier
2010-06-01 8:19 ` Juanma Barranquero
2010-06-01 8:33 ` David Kastrup [this message]
2010-06-01 13:12 ` Stefan Monnier
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=876323b1a9.fsf@lola.goethe.zz \
--to=dak@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 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).