From: Kip Macy <kip.macy@gmail.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: Jerone Young <jyoung5@us.ibm.com>,
xen-devel <xen-devel@lists.sourceforge.net>,
ian.pratt@cl.cam.ac.uk
Subject: Re: Perferred way for Patch Submission (inline or attchment)?
Date: Sun, 20 Mar 2005 11:54:18 -0800 [thread overview]
Message-ID: <b1fa291705032011544626fe08@mail.gmail.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D1E3767@liverpoolst.ad.cl.cam.ac.uk>
I like to post patches as links because the patches can be very large
and I like to know how many people are looking at them. For example
I've had 13 accesses to my recent ptrace patch. Granted, its not a /.,
but it does tell me that people are actually using or thinking about
using the domu_debug code.
Is this OK going forward?
-Kip
On Sun, 20 Mar 2005 10:30:32 -0000, Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk> wrote:
>
>
> > I'm wondering do you guys prefer we submit patches as attachments or
> > inline them in the email? Inline in emails have become the standard
> > everywhere else, what is the preferred way you guys would like patches
> > submitted to the list.... inline or attachments?
>
> Inline in emails is probably best, but I personally don't have a strong
> opinion. We just use the bktools package to extract them.
>
> I haven't found a good way of keeping any per-file comments with the
> files, but I think Christian has some magic script that's able to
> extract and check these in too.
>
> Ian
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_ide95&alloc_id\x14396&opclick
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xen-devel
>
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click
next prev parent reply other threads:[~2005-03-20 19:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-20 10:30 Perferred way for Patch Submission (inline or attchment)? Ian Pratt
2005-03-20 19:54 ` Kip Macy [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-20 6:09 Jerone Young
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=b1fa291705032011544626fe08@mail.gmail.com \
--to=kip.macy@gmail.com \
--cc=ian.pratt@cl.cam.ac.uk \
--cc=jyoung5@us.ibm.com \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=xen-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.