From: Glenn Morris <rgm@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: emacs-devel@gnu.org
Subject: Re: namespace convention for short-lived branches
Date: Wed, 22 Apr 2015 13:56:49 -0400 [thread overview]
Message-ID: <m7d22w2gim.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <5535562D.5050808@yandex.ru> (Dmitry Gutov's message of "Mon, 20 Apr 2015 22:40:29 +0300")
Dmitry Gutov wrote:
> If the branch contents are simply merged, will the mailed send out the
> contents of every commit therein again?
Well, AFAICS it sends out the relevant information that I think it should?
That's why I'm personally not interested in seeing the diffs for
"work-in-progress" branches. I'll read them when/if they go to master.
You can verify this by looking at the mails that come about when
emacs-24 is merged to trunk, eg:
http://lists.gnu.org/archive/html/emacs-diffs/2015-03/msg00037.html
There have been no complaints so far.
At the risk of opening the chat-about-git-floodgates again, this prompts
me to ask: is there a setting that will make such merge mails better?
I'm using
log --format=full -C --stat -p -m --first-parent
I'm a simple-minded person who just wants to see
"difference between master before this change was applied and after it
was applied"
Sometimes the diffs don't seem to make sense. Eg in
http://lists.gnu.org/archive/html/emacs-diffs/2015-03/msg00040.html
The NEWS diff is completely bogus AFAICS (the NEWS file in emacs-24
merges to NEWS.24 in trunk).
next prev parent reply other threads:[~2015-04-22 17:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-20 16:20 namespace convention for short-lived branches Glenn Morris
2015-04-20 19:08 ` Stefan Monnier
2015-04-21 11:04 ` Oleh Krehel
2015-04-21 14:12 ` Stefan Monnier
2015-04-21 19:00 ` Achim Gratz
2015-04-21 19:00 ` Oleh Krehel
2015-04-21 19:21 ` Achim Gratz
2015-04-21 19:26 ` Achim Gratz
2015-04-20 19:40 ` Dmitry Gutov
2015-04-22 17:56 ` Glenn Morris [this message]
2015-04-23 1:03 ` Dmitry Gutov
2015-04-21 10:54 ` Phillip Lord
2015-04-21 11: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=m7d22w2gim.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=dgutov@yandex.ru \
--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.