0 index (this message)
1 add /proc/*/pmap files
2 remove /proc/*/smaps files (depends on #1)
3 fix integer overflow (depends on #2)
4 fix permissions (depends on #2)
I found an old email account that still supports adding raw binay data
to an email message body. I really wish we could get away from this,
because it makes contributions damn near impossible for some people.
Other people are far worse off than I am.
These all apply to -git4, grabbed Saturday night.
On 1/22/06, Albert D. Cahalan <[email protected]> wrote:
>
[snip]
>
> I found an old email account that still supports adding raw binay data
> to an email message body. I really wish we could get away from this,
1. having patches inline in messages instead of as attachments make
initial viewing of the patches much easier - no need to open a
sepperate attachment just to review a patch.
2. Commenting on patches is a lot easier when you can just reply to
the message and have the patch quoted inline and then add your
comments.
3. saving patches for application is easy when you can just save the
email message with the patch inline - then you have the explanation of
the patch and the patch itself nicely contained in a single file (and
patch will conveniently strip the extra text before the patch-proper
when you apply it).
4. You don't need an account that's able to add 'binary data' -
patches should preferable be in 7-bit ASCII text form, not 8-bit.
And if your current MUA doesn't allow you to add text files inline,
then there are several that do - mutt, pine & kmail come to mind and
there are several others.
> because it makes contributions damn near impossible for some people.
> Other people are far worse off than I am.
>
I'm currious - in what situations are you prevented from sending
patches inline in emails??
--
Jesper Juhl <[email protected]>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
On Sun, 22 Jan 2006 17:15:24 -0500 (EST) Albert D. Cahalan wrote:
>
> 0 index (this message)
> 1 add /proc/*/pmap files
> 2 remove /proc/*/smaps files (depends on #1)
> 3 fix integer overflow (depends on #2)
> 4 fix permissions (depends on #2)
>
> I found an old email account that still supports adding raw binay data
> to an email message body. I really wish we could get away from this,
> because it makes contributions damn near impossible for some people.
> Other people are far worse off than I am.
perhaps a gmail account would help?
and use their POP interface instead of webmail...
---
~Randy