From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Lars Magne Ingebrigtsen <larsi@gnus.org>
Cc: emacs-devel@gnu.org
Subject: Re: [emacs] 02/02: Get rid of arbitrary gnutls length limit
Date: Tue, 18 Nov 2014 12:38:16 -0500 [thread overview]
Message-ID: <jwv61ecjtu9.fsf-monnier+emacsdiffs@gnu.org> (raw)
In-Reply-To: <m3d28kfnmv.fsf@stories.gnus.org> (Lars Magne Ingebrigtsen's message of "Tue, 18 Nov 2014 18:02:16 +0100")
>>> Get rid of arbitrary gnutls length limit
>> Please use ChangeLog-style message formatting.
> When applying to the trunk, we're not going to keep any of the commits,
> are we? I though we were going to flatten the entire thing into one
> commit, and for that the ChangeLog entries that are in there are
> sufficient.
I think the branches in emacs.git should follow our coding guidelines
(just like they have to follow the copyright assignment policy).
We can be a bit more permissive if the final "merge" drops the metadata
(i.e. is not an actual merge), but I'd rather we try to follow the
same rules. Otherwise we'll have two different kinds of branches
(those that can be merged, and those whose metadata needs to be thrown
away) and we need to keep track of which is which, and pay attention to
those details in the emacs-diffs we receive, etc...
Stefan
next prev parent reply other threads:[~2014-11-18 17:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20141118015733.28605.78162@vcs.savannah.gnu.org>
[not found] ` <E1XqY2w-0007SO-Er@vcs.savannah.gnu.org>
2014-11-18 16:50 ` [emacs] 02/02: Get rid of arbitrary gnutls length limit Stefan Monnier
2014-11-18 17:02 ` Lars Magne Ingebrigtsen
2014-11-18 17:38 ` Stefan Monnier [this message]
2014-11-18 17:40 ` Lars Magne Ingebrigtsen
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=jwv61ecjtu9.fsf-monnier+emacsdiffs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.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.