unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: 15310@debbugs.gnu.org
Subject: bug#15310: 24.3.50; [ELPA] Better commit notifications for upstream authors
Date: Mon, 09 Sep 2013 00:56:40 +0300	[thread overview]
Message-ID: <871u4znfjb.fsf@yandex.ru> (raw)

Currently, when there are some changes made to a package that has an
upstream, an email gets sent for each group of commits pushed, to
upstream author (or authors, I'm assuming).

When the notification does come, getting the required changes out is not
as easy as it could be.

The commits are all sent together (one notification email per push,
AFAICS), as a plain-text email without attachments.

I have to identify the ones that originated from ELPA, and weren't
synced from upstream, or just sync commits, for each of them copy the
diff to a file manually, and separately copy the message and the author
when making the commit.

Since all paths the such diffs contain "a/packages/<package-name>", I
also have to run a replace command before applying the diff.

Is there a better way to work with these emails?

If no, it would be better if, for example, the script preparing these
emails identified commits not synced from upstream (maybe by file paths
inside the diffs?), fixed the paths, and attached these commits in patch
format that's accepted by 'git am' and already contains the commit
message and author information.





             reply	other threads:[~2013-09-08 21:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-08 21:56 Dmitry Gutov [this message]
2013-09-11 17:09 ` bug#15310: 24.3.50; [ELPA] Better commit notifications for upstream authors Stefan Monnier
2021-05-30  6:00   ` Lars Ingebrigtsen
2021-07-02 11:15     ` Lars 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

  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=871u4znfjb.fsf@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=15310@debbugs.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 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).