From: Dmitry Gutov <dgutov@yandex.ru>
To: Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel <emacs-devel@gnu.org>
Subject: Re: [ELPA-diffs] /srv/bzr/emacs/elpa r374: company: Release 0.6.2
Date: Sun, 24 Mar 2013 05:05:40 +0400 [thread overview]
Message-ID: <514E5164.9090901@yandex.ru> (raw)
In-Reply-To: <jwvehf5pr68.fsf-monnier+emacs@gnu.org>
Stefan Monnier <monnier@iro.umontreal.ca> wrote:
>> message:
>> company: Release 0.6.2
>
>Please include the usual description of changes in your ELPA commit
>messages: there is no ChangeLog file, but the "bzr log" should give the
>same information.
What's the recommended way to automatically pull commit messages from
Git to Bazaar? What if the Git repo has some files that Bazaar doesn't?
At the moment there are two such files: Makefile and NEWS.md, the first
of them doesn't seem right to be included in the package tar, and the
second one doesn't have any license header, AFAIK there's no place to
put it, but I expect that without it, the package won't build.
I'd also like to know if it's a new requirement: I've been "merging"
changes from the upstream js2-mode repo for a while, and most of those
commits also didn't have descriptive messages.
next parent reply other threads:[~2013-03-24 1:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1UJXgb-000646-9w@vcs.savannah.gnu.org>
[not found] ` <jwvehf5pr68.fsf-monnier+emacs@gnu.org>
2013-03-24 1:05 ` Dmitry Gutov [this message]
2013-03-24 14:14 ` [ELPA-diffs] /srv/bzr/emacs/elpa r374: company: Release 0.6.2 Stefan Monnier
2013-03-25 11:20 ` Dmitry Gutov
2013-03-30 4:33 ` Dmitry Gutov
2013-03-30 17:12 ` Stefan Monnier
2013-03-30 17:49 ` Dmitry Gutov
2013-04-03 17:32 ` 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=514E5164.9090901@yandex.ru \
--to=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).