unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 19113@debbugs.gnu.org, Paul Eggert <eggert@cs.ucla.edu>
Subject: bug#19113: Generate a ChangeLog file from commit logs
Date: Sat, 06 Dec 2014 04:27:22 +0200	[thread overview]
Message-ID: <86mw71pl6d.fsf@yandex.ru> (raw)
In-Reply-To: <jwv8uimx7an.fsf-monnier+emacsbugs@gnu.org> (Stefan Monnier's message of "Fri, 05 Dec 2014 13:49:02 -0500")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>> This is, of course, the PR system you find on Github and such sites.
>
> That's also the "patch queue management" I mentioned earlier.

Right. On GitHub, it's often also a decent platform for discussions.

> Because nobody has set such a thing up (and AFAICT Savannah doesn't
> have such a thing built-in, oddly enough).

It shouldn't be too hard, actually, to set up some code review tool,
such as Gerrit [0], Review Board [1] or Differential [2].

I think all of them support automatic merging of approved patches, or at
least make it reasonably easy. The last one seems to offer a lot of
options, at the cost of learning the whole Phabricator ecosystem.

What do you see as requirements for such a tool? Integration with
Savannah user database?

Do you like at least one of them?

I'd also welcome opinions from people who have experience working with
them, because honestly, I've only done in-browser code reviews
inside issue tracking tools, such as GitHub and GitLab.

[0] https://code.google.com/p/gerrit/
[1] https://www.reviewboard.org/
[2] http://phabricator.org/applications/differential/





  parent reply	other threads:[~2014-12-06  2:27 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-19 23:57 bug#19113: Generate a ChangeLog file from commit logs Paul Eggert
2014-11-20 15:51 ` Eli Zaretskii
2014-11-20 17:43   ` Paul Eggert
2014-11-20 17:44   ` Paul Eggert
2014-11-26  5:38     ` Paul Eggert
2014-11-26  6:21       ` Jan D.
2014-11-26  7:50         ` Paul Eggert
2014-11-26 15:12       ` Stefan Monnier
2014-11-26 19:16         ` Paul Eggert
2014-11-26 22:15           ` Stefan Monnier
2014-12-05  8:07           ` Glenn Morris
2014-12-05  8:38             ` Eli Zaretskii
2014-12-05 14:33             ` Ted Zlatanov
2014-12-05 18:49               ` Stefan Monnier
2014-12-05 20:08                 ` Ted Zlatanov
2014-12-06  4:59                   ` Stefan Monnier
2014-12-06 13:17                     ` Ted Zlatanov
2014-12-06  2:27                 ` Dmitry Gutov [this message]
2014-12-06  5:06                   ` Stefan Monnier
2014-12-06  7:26                     ` Eli Zaretskii
2014-12-09 13:46                     ` Dmitry Gutov
2014-12-05 15:38             ` Stefan Monnier
2014-12-06  4:42               ` Paul Eggert
2014-12-06  7:40                 ` Eli Zaretskii
2014-12-09  5:14                 ` Glenn Morris
2014-12-09  6:42                   ` Paul Eggert
2015-01-03  1:37             ` Glenn Morris
2014-11-20 18:00   ` Achim Gratz
2014-11-20 17:25 ` Pádraig Brady
2015-01-12  7:38 ` Paul Eggert
2015-01-15 14:58   ` Stefan Monnier
2015-01-15 21:46   ` Glenn Morris
2015-01-16  1:27     ` Paul Eggert
2015-01-30 16:34       ` Stefan Monnier
2015-01-30 20:14         ` Paul Eggert
2015-01-31  6:33           ` Stefan Monnier
2015-01-31  8:18             ` Paul Eggert
2015-01-31  9:06           ` Andreas Schwab
2015-03-21  2:37 ` Paul Eggert
2015-03-21  8:33   ` Eli Zaretskii
2015-03-21 14:38     ` Stefan Monnier
2015-03-22 23:53   ` Glenn Morris
2015-04-07  7:06   ` Paul Eggert

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=86mw71pl6d.fsf@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=19113@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    --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).