Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Git, ding-cvslog  (gmane.emacs.gnus.cvs), ding-patches (gmane.emacs.gnus.commits)
Date: Wed, 01 Sep 2010 15:30:35 -0500	[thread overview]
Message-ID: <87occh6wb8.fsf@lifelogs.com> (raw)
In-Reply-To: <87wrr58b9u.fsf@topper.koldfront.dk>

On Wed, 01 Sep 2010 22:22:05 +0200 asjo@koldfront.dk (Adam Sjøgren) wrote: 

AS> I am trying to sort of follow what happens by looking at the emails, and
AS> to me everything before the:

AS>   - Log -----------------------------------------------------------------

AS> -line is noise (or stuff I would be happy to scroll down and look at, in
AS> the rare cases I need that information). While log and diff are the
AS> parts I most often want to read.

AS> So I suggest that the part that looks like this at the top:

AS>          via  f95141317eb39d9290d2fb9e7794b42db17b8991 (commit)
AS>         from  d7c1cd6edd6b738730b0a646b7e8a257d30194df (commit)

AS>   Those revisions listed above that are new to this repository have
AS>   not appeared on any other notification email; so we list those
AS>   revisions in full, below.

AS> also is moved after the log and diff-parts.

I can do it, sure, but the revision list is a table of contents and
pretty nice in any non-trivial situation so I'd leave it on top.  Would
something like the following work for you?

Ted


diff --git a/etc/post-receive b/etc/post-receive
index 37ec5f9..9309ea3 100755
--- a/etc/post-receive
+++ b/etc/post-receive
@@ -405,10 +405,6 @@ generate_update_branch_email()
 
 	echo ""
 	if [ -z "$rewind_only" ]; then
-		echo "Those revisions listed above that are new to this repository have"
-		echo "not appeared on any other notification email; so we list those"
-		echo "revisions in full, below."
-
 		echo ""
 		echo $LOGBEGIN
 		show_new_revisions
@@ -418,6 +414,11 @@ generate_update_branch_email()
 		# revisions added by this update" message
 
 		echo $LOGEND
+
+		echo "Those revisions listed above that are new to this repository have"
+		echo "not appeared on any other notification email; so we listed those"
+		echo "revisions in full, above."
+
 	else
 		echo "No new revisions were added by this update."
 	fi




      parent reply	other threads:[~2010-09-01 20:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-01  7:44 Reiner Steib
2010-09-01 11:18 ` Ted Zlatanov
2010-09-01 11:21   ` Ted Zlatanov
2010-09-01 14:36   ` Jason L Tibbitts III
2010-09-01 20:22   ` Adam Sjøgren
2010-09-01 20:28     ` Lars Magne Ingebrigtsen
2010-09-02  2:42       ` Ted Zlatanov
2010-09-02  2:57         ` Lars Magne Ingebrigtsen
2010-09-02 10:05           ` Ted Zlatanov
2010-09-02 10:55         ` Adam Sjøgren
2010-09-02 12:31           ` Ted Zlatanov
2010-09-02 14:28             ` Lars Magne Ingebrigtsen
2010-09-01 20:30     ` Ted Zlatanov [this message]

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=87occh6wb8.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=ding@gnus.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.
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 NNTP newsgroup(s).