linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Welch, Martyn (GE EntSol,
	Intelligent Platforms)" <martyn.welch@gefanuc.com>
Cc: "Lissaman, Stuart \(GE EntSol,
	Intelligent Platforms\)" <stuart.lissaman@gefanuc.com>,
	linuxppc-embedded@ozlabs.org
Subject: Re: Suitability of patchs as attachments
Date: Fri, 16 May 2008 09:53:57 -0600	[thread overview]
Message-ID: <fa686aa40805160853ube181b8k2ef79fcc783613d4@mail.gmail.com> (raw)
In-Reply-To: <1CADFA951940554D86FBD8B24BBFF3A00129CBF5@LONMLVEM08.e2k.ad.ge.com>

On Fri, May 16, 2008 at 2:46 AM, Welch, Martyn (GE EntSol, Intelligent
Platforms) <martyn.welch@gefanuc.com> wrote:
> Hi all,
>
> I wish I didn't have to ask this but...
>
> For now I'm stuck using Outlook and Exchange for email, despite my best
> efforts I have been unable to force it to send patchs inline without
> breaking them (I can get it to do plain text, however it seems to have
> the habbit of wrapping ling lines, such as the "diff --git..." lines).
>
> Is anyone in the same position and has worked out how to do this?

Yes, don't use your email client for actually sending the patches.
Use git-send-email for 'stg mail' to send your patches from the
command line.  Your Exchange server should have SMTP turned on and you
can send directly to it.  Otherwise, you can try connecting to an
external open SMTP relay.

You'll still receive the replies and comments in Outlook.

Cheers,
g.

>
> I also have a patch for initial support of one of our boards waiting
> here, would it be acceptable to attach this as a patch on this mailing
> list?
>
> Thanks,
>
> Martyn
>
> ----
> Martyn Welch MEng MPhil MIET
> Principal Software Engineer
>
> GE Fanuc Intelligent Platforms
> Tove Valley Business Park, Towcester,
> Northants, NN12 6PF, United Kingdom
>
> Telephone: +44 (0) 1327 359444
> Direct Dial: +44 (0) 1327 322748
> Fax: +44 (0) 1327 322800
> email: martyn.welch@gefanuc.com
> web: www.gefanuc.com
>
> GE Fanuc Intelligent Platforms Ltd, registered in England and Wales
> (3828642) at 100 Barbirolli Square, Manchester, M2 3AB, VAT GB 729 849
> 476
>
> GE Fanuc Intelligent Platforms Confidential and Proprietary. If you have
> received this message in error please notify us immediately and
> permanently remove it from your system and destroy any printed
> hardcopies.
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>



-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.

      parent reply	other threads:[~2008-05-16 15:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-16  8:46 Suitability of patchs as attachments Welch, Martyn (GE EntSol, Intelligent Platforms)
2008-05-16 13:28 ` Josh Boyer
2008-05-16 15:53 ` Grant Likely [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=fa686aa40805160853ube181b8k2ef79fcc783613d4@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=martyn.welch@gefanuc.com \
    --cc=stuart.lissaman@gefanuc.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 NNTP newsgroup(s).