all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: sds@gnu.org
Cc: emacs-devel@gnu.org
Subject: Re: master e45dbdc: package--ensure-init-file: widen requires	save-restriction
Date: Wed, 15 Apr 2015 20:34:44 +0300	[thread overview]
Message-ID: <83d2359txn.fsf@gnu.org> (raw)
In-Reply-To: <m2a8y9ianv.fsf@gnu.org>

> From: Sam Steingold <sds@gnu.org>
> Date: Wed, 15 Apr 2015 13:06:12 -0400
> 
> > * Glenn Morris <etz@tah.bet> [2015-04-15 11:32:35 -0400]:
> >
> > Sam Steingold wrote:
> >
> >> Commit: Sam Steingold <sds@gnu.org>
> >>
> >>     package--ensure-init-file: widen requires save-restriction
> >
> > Please use a ChangeLog-like format for your commit messages. Eg
> >
> > * lisp/emacs-lisp/package.el (package--ensure-init-file): Save restriction.
> 
> I am confused.
> We can get file information from git.
> Why do we need to introduce this constraint on messages just as we
> celebrating liberation from ChangeLog files?

How else do you expect the ChangeLog to be generated in its correct
format at release time?  By what magic?



  reply	other threads:[~2015-04-15 17:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20150414191903.31102.28462@vcs.savannah.gnu.org>
     [not found] ` <E1Yi6MR-00086O-AO@vcs.savannah.gnu.org>
2015-04-15 15:32   ` master e45dbdc: package--ensure-init-file: widen requires save-restriction Glenn Morris
2015-04-15 16:21     ` Stefan Monnier
2015-04-15 17:20       ` Glenn Morris
2015-04-15 19:26         ` Stefan Monnier
2015-04-15 17:06     ` Sam Steingold
2015-04-15 17:34       ` Eli Zaretskii [this message]
2015-04-15 18:55         ` Sam Steingold
2015-04-15 19:14           ` Eli Zaretskii

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=83d2359txn.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=sds@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 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.