From: Eli Zaretskii <eliz@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: scratch/gnus-cloud ece27ed 01/61: Merge branch 'master' of git.sv.gnu.org:/srv/git/emacs
Date: Fri, 01 Jul 2016 21:46:49 +0300 [thread overview]
Message-ID: <83lh1ltcva.fsf@gnu.org> (raw)
In-Reply-To: <87inwpjlnc.fsf@lifelogs.com> (message from Ted Zlatanov on Fri, 01 Jul 2016 13:47:19 -0400)
> From: Ted Zlatanov <tzz@lifelogs.com>
> Date: Fri, 01 Jul 2016 13:47:19 -0400
>
> On Fri, 1 Jul 2016 17:37:50 +0000 (UTC) tzz@lifelogs.com (Teodor Zlatanov) wrote:
>
> TZ> branch: scratch/gnus-cloud
> TZ> commit ece27ed21920283af9af1d78bd5235bf6097fce1
> TZ> Merge: 743e6b6 13feb31
> TZ> Author: Ted Zlatanov <tzz@lifelogs.com>
> TZ> Commit: Ted Zlatanov <tzz@lifelogs.com>
>
> TZ> Merge branch 'master' of git.sv.gnu.org:/srv/git/emacs
>
> Maybe the notification script should skip merge commits or ignore
> scratch branches? It just sent out a whole bunch of notifications for a
> scratch branch.
Why did you make so many merges from master onto the scratch branch?
This shouldn't be necessary to begin with.
next prev parent reply other threads:[~2016-07-01 18:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160701173748.21438.91559@vcs.savannah.gnu.org>
[not found] ` <20160701173750.9F5F1220067@vcs.savannah.gnu.org>
2016-07-01 17:47 ` scratch/gnus-cloud ece27ed 01/61: Merge branch 'master' of git.sv.gnu.org:/srv/git/emacs Ted Zlatanov
2016-07-01 18:46 ` Eli Zaretskii [this message]
2016-07-01 19:53 ` Ted Zlatanov
2016-07-02 6:29 ` Eli Zaretskii
2016-07-05 2:38 ` Ted Zlatanov
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=83lh1ltcva.fsf@gnu.org \
--to=eliz@gnu.org \
--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).