unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: David Engster <deng@randomsample.de>
Cc: hi@yagnesh.org, eggert@cs.ucla.edu, bruce.connor.am@gmail.com,
	emacs-devel@gnu.org
Subject: Re: ChangeLog and the release branch
Date: Sat, 28 Nov 2015 14:14:17 +0200	[thread overview]
Message-ID: <83oaeepbhi.fsf@gnu.org> (raw)
In-Reply-To: <87bnaepckp.fsf@isaac.fritz.box>

> From: David Engster <deng@randomsample.de>
> Cc: Yagnesh Raghava Yakkala <hi@yagnesh.org>,  bruce.connor.am@gmail.com,  emacs-devel@gnu.org, Paul Eggert <eggert@cs.ucla.edu>
> Date: Sat, 28 Nov 2015 12:50:46 +0100
> 
> > How do you store the diffs in Git notes?  You can't easily write diffs
> > by hand, so some script is needed to generate them and put them there.
> 
> I don't think you would store a diff there but the complete, corrected
> ChangeLog.

That, too, needs some help, no?  It's easy to format ChangeLog entries
when actually editing a ChangeLog file.  It's probably harder to do
that when editing a Git note.

> If someone is volunteering to actually set this up and deal with the
> aftermath of people struggling with 'git notes', then yes.

Could you tell what that "struggling" entails?  I never used Git
notes, so I don't know what difficulties and gotchas this could
present.



  reply	other threads:[~2015-11-28 12:14 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-23 20:36 When do we merge the commits from emacs-25 onto master? Artur Malabarba
2015-11-23 20:51 ` Eli Zaretskii
2015-11-23 22:05 ` Paul Eggert
2015-11-23 22:34   ` Artur Malabarba
2015-11-23 22:43     ` David Engster
2015-11-24 14:25       ` ChangeLog and the release branch (was: When do we merge the commits from emacs-25 onto master?) Artur Malabarba
2015-11-24 13:29         ` ChangeLog and the release branch Dmitry Gutov
2015-11-24 16:24         ` ChangeLog and the release branch (was: When do we merge the commits from emacs-25 onto master?) Eli Zaretskii
2015-11-26 21:07           ` ChangeLog and the release branch Yagnesh Raghava Yakkala
2015-11-27  7:26             ` Eli Zaretskii
2015-11-28 11:50               ` David Engster
2015-11-28 12:14                 ` Eli Zaretskii [this message]
2015-11-28 12:36                   ` David Engster
2015-11-28 19:15                     ` John Wiegley
2015-11-24 18:32       ` When do we merge the commits from emacs-25 onto master? Eli Zaretskii
2015-11-24 19:33         ` David Engster
2015-11-24 19:46         ` Paul Eggert
2015-11-24 20:14           ` Eli Zaretskii
2015-11-24 22:04             ` Paul Eggert
2015-11-25  0:35               ` David Engster
2015-11-25  6:32                 ` Paul Eggert
2015-11-25 18:18                   ` Eli Zaretskii
2015-11-25 18:16                 ` 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

  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=83oaeepbhi.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=bruce.connor.am@gmail.com \
    --cc=deng@randomsample.de \
    --cc=eggert@cs.ucla.edu \
    --cc=emacs-devel@gnu.org \
    --cc=hi@yagnesh.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).