From: Ted Zlatanov <tzz@lifelogs.com>
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 15:53:15 -0400 [thread overview]
Message-ID: <8760spjftg.fsf@lifelogs.com> (raw)
In-Reply-To: 83lh1ltcva.fsf@gnu.org
On Fri, 01 Jul 2016 21:46:49 +0300 Eli Zaretskii <eliz@gnu.org> wrote:
>> 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.
EZ> Why did you make so many merges from master onto the scratch branch?
EZ> This shouldn't be necessary to begin with.
The point is that it's a scratch branch. I'm asking for these branches
to be excluded from diffs, otherwise I'll have to use another Git server
so I'm not spamming emacs-diffs.
FWIW, I merge the current master into my branch to make sure it works
fine. This is automated so it happens all the time, and I will rebase,
squash, and adjust the commit messages when it's time to push the code
to a public branch. But all that is not relevant, there are many ways to
generate noise in scratch branches.
Ted
next prev parent reply other threads:[~2016-07-01 19:53 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
2016-07-01 19:53 ` Ted Zlatanov [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8760spjftg.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.