unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: David Engster <deng@randomsample.de>
Cc: emacs-devel@gnu.org
Subject: Re: Disable emacs-diffs mails for scratch branches
Date: Sat, 28 Jan 2017 21:09:10 -0500	[thread overview]
Message-ID: <jwv7f5ek4df.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87o9yqzyq0.fsf@engster.org> (David Engster's message of "Sat, 28 Jan 2017 22:00:39 +0100")

>>> Subject says it all. Could we please do that? I think it's pretty normal
>>> for scratch-Branches being deleted and pushed anew, and for large
>>> branches like cedet-merge or cedet-tests this needlessly creates
>>> hundreds of mails each time.
>> I agree that those 300 emails dumps are more annoying than useful.
>> But FWIW, I see two problems with your suggestion:
>> 1- I don't know how to do it.
> We'd have to adapt the post-receive hook, or whatever else is triggering
> the mails.

Yes, that much I know, but I also know that we don't have direct access
to it.  So it depends on Savannah admins, and if I was them I wouldn't
just accept random patches, since AFAIK they use an existing mail-hook
and so they probably want to stay close to the upstream version to be
able to incorporate future changes.

So, we should figure out exactly what choices we have available.

>> 2- I do find it very useful to see commits on scratch branches when
>> those branches are used for gradual development (e.g. the byte-switch
>> branch).
> How about simply not naming those branches with the 'scratch' prefix,
> then?  I was under the impression that 'scratch' means "can be
> force-pushed/deleted any time, don't base your work onto it".

AFAICT the byte-switch does belong to scratch.  Being able/allowed to
force-push/delete doesn't mean that you have to do it all the time.


        Stefan



  reply	other threads:[~2017-01-29  2:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-28  9:56 Disable emacs-diffs mails for scratch branches David Engster
2017-01-28 15:35 ` Stefan Monnier
2017-01-28 21:00   ` David Engster
2017-01-29  2:09     ` Stefan Monnier [this message]
2017-01-29  2:31 ` Lars Ingebrigtsen
2017-01-29  9:59   ` David Engster

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=jwv7f5ek4df.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=deng@randomsample.de \
    --cc=emacs-devel@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).