From: Sami Wagiaalla <swagiaal@redhat.com>
To: Mark Wielaard <mark@klomp.org>
Cc: Tim Moore <timoore@redhat.com>, frysk <frysk@sourceware.org>
Subject: Re: frysk git repository
Date: Fri, 26 Oct 2007 18:38:00 -0000 [thread overview]
Message-ID: <4722342E.5030506@redhat.com> (raw)
In-Reply-To: <1193417804.2931.25.camel@hermans.wildebeest.org>
> 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.
next prev parent reply other threads:[~2007-10-26 18:38 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 [this message]
2007-10-29 8:19 ` Mark Wielaard
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=4722342E.5030506@redhat.com \
--to=swagiaal@redhat.com \
--cc=frysk@sourceware.org \
--cc=mark@klomp.org \
--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).