From: Tim Moore <timoore@redhat.com>
To: Mark Wielaard <mark@klomp.org>
Cc: frysk <frysk@sourceware.org>
Subject: Re: frysk git repository
Date: Fri, 26 Oct 2007 16:35:00 -0000 [thread overview]
Message-ID: <4722171D.2020005@redhat.com> (raw)
In-Reply-To: <1193410781.2931.2.camel@hermans.wildebeest.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Mark Wielaard wrote:
> Hi Tim,
>
> On Wed, 2007-10-24 at 19:09 +0200, Tim Moore wrote:
>> Also, commit messages make most sense in the git world, with the various tools that print
>> out logs, if you begin your message with a one-line summary, and a blank line. After that
>> you can include the ChangeLog entries we have now.
>
> Is there a way to include the actual diffs of the patches that are
> pushed into the repo to the commit list to make reviewing changes
> easier?
I can tweak the script, but I think that falls into the category of "too much information"
since you can review the changes locally using either the git command line tools or
gitk.
Tim
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFHIha5eDhWHdXrDRURAgUFAJ9QXRBtpOYIrgDfjD2uJn86OjdT2ACdF3k2
lZgnMyItckan7938zVdFbCA=
=eHgY
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2007-10-26 16:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-24 17:09 Tim Moore
2007-10-24 17:20 ` Elena Zannoni
2007-10-25 4:50 ` Tim Moore
2007-10-24 19:51 ` Mark Wielaard
2007-10-24 20:05 ` Mark Wielaard
2007-10-25 4:48 ` Tim Moore
2007-10-25 20:10 ` Andrew Cagney
2007-10-26 14:52 ` frysk git repository (workflow) Sami Wagiaalla
2007-10-27 17:58 ` Tim Moore
2007-10-26 14:59 ` frysk git repository Mark Wielaard
2007-10-26 16:33 ` Tim Moore
2007-10-26 16:57 ` Mark Wielaard
2007-10-26 18:38 ` Sami Wagiaalla
2007-10-29 8:19 ` Mark Wielaard
2007-10-30 17:20 ` Andrew Cagney
2007-10-26 16:35 ` Tim Moore [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=4722171D.2020005@redhat.com \
--to=timoore@redhat.com \
--cc=frysk@sourceware.org \
--cc=mark@klomp.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 read-only IMAP folder(s) and NNTP newsgroup(s).