From: Nicolas Petton <nicolas@petton.fr>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Nicolas Petton <nicolas@petton.fr>,
monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Preparing for 24.5
Date: Wed, 04 Feb 2015 02:17:03 +0100 [thread overview]
Message-ID: <87386mzd9s.fsf@petton.fr> (raw)
In-Reply-To: <831tm9ii57.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Nicolas Petton <nicolas@petton.fr>
>> Date: Sun, 01 Feb 2015 19:39:32 +0100
>>
>> Now I still have an issue with the following 3 files, and I'm not sure
>> if they should just be ignored:
>>
>> info/dir
>
> Ignore it, it's automatically generated these days.
>
>> notes/changelogs
>
> This was merged to notes/repo, so I guess treat it as renamed.
>
>> gnus-coding.txt
>
> I have no idea what that is. Maybe someone else does.
>
>> Also, should I add a changelog entry when fixing the changelog itself?
>
> No.
Thank you.
I completed all the steps in admin/make-tarball.txt except for
uploading, and committed the changes to the emacs-24 branch.
I haven't uploaded the tarball yet as I'm waiting for an answer from the
ftp admins. Also, since it's the first time I'm doing this, would
someone like to double check it?
Cheers,
Nico
--
Nicolas Petton
http://nicolas-petton.fr
next prev parent reply other threads:[~2015-02-04 1:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-30 16:10 Preparing for 24.5 Stefan Monnier
2015-01-30 16:21 ` Nicolas Petton
2015-01-30 16:25 ` Eli Zaretskii
2015-02-01 18:19 ` Nicolas Petton
2015-02-01 18:39 ` Nicolas Petton
2015-02-01 18:47 ` Eli Zaretskii
2015-02-04 1:17 ` Nicolas Petton [this message]
2015-02-04 3:46 ` Eli Zaretskii
2015-02-04 9:57 ` Nicolas Petton
2015-02-04 15:26 ` Eli Zaretskii
2015-02-04 16:39 ` Nicolas Petton
2015-02-05 16:20 ` Eli Zaretskii
2015-02-06 12:19 ` Nicolas Petton
2015-02-04 15:20 ` Stefan Monnier
2015-02-04 15:53 ` Nicolas Petton
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=87386mzd9s.fsf@petton.fr \
--to=nicolas@petton.fr \
--cc=eliz@gnu.org \
--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 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.