From: Mark Wielaard <mark@klomp.org>
To: Sami Wagiaalla <swagiaal@redhat.com>
Cc: Tim Moore <timoore@redhat.com>, frysk <frysk@sourceware.org>
Subject: Re: frysk git repository
Date: Mon, 29 Oct 2007 08:19:00 -0000 [thread overview]
Message-ID: <1193645936.3830.17.camel@dijkstra.wildebeest.org> (raw)
In-Reply-To: <4722342E.5030506@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 957 bytes --]
Hi,
On Fri, 2007-10-26 at 14:38 -0400, Sami Wagiaalla wrote:
> > There is never too much information!
> Its not too much information but it might be too big in size.
> If that is not an issue then I would like to see the patches
> in the email as well. Having them inlined in the email it self
> and not as attachments would be best.
Yes. For Mercurial I would use something like the following:
[hooks]
incoming.notify = python:hgext.notify.hook
[notify]
sources = serve push pull bundle
maxdiff = 500
[usersubs]
fedora-hg-list@klomp.org = /hg/fedora
[smtp]
host = localhost
Which makes sure emails are send (by the notify extension), but diffs
are capped at 500 lines max (and then you get a link to the hg webrepo
to retrieve the full diff of the changeset). Hopefully there is
something similar for git.
Cheers,
Mark
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-10-29 8:19 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 [this message]
2007-10-30 17:20 ` Andrew Cagney
2007-10-26 16:35 ` Tim Moore
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=1193645936.3830.17.camel@dijkstra.wildebeest.org \
--to=mark@klomp.org \
--cc=frysk@sourceware.org \
--cc=swagiaal@redhat.com \
--cc=timoore@redhat.com \
/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).