<div dir="ltr">Wow, I couldn't expect all these detailed replies and yes, I haven't seen this way to deal with patches yet but thank you all for the help, I'll figure out following your instructions and now I know what to google too :-)<div>
<br></div><div>Best Regards</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jun 25, 2014 at 5:56 AM, Jasper St. Pierre <span dir="ltr"><<a href="mailto:jstpierre@mecheye.net" target="_blank">jstpierre@mecheye.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><div class="h5">On Wed, Jun 25, 2014 at 2:59 AM, Lyude <span dir="ltr"><<a href="mailto:thatslyude@gmail.com" target="_blank">thatslyude@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>On Tue, 2014-06-24 at 23:40 -0700, Andrea Giammarchi wrote:<br>
> Yeah Peter, I know how to apply a patch and no, I don't have any of<br>
> them in my inbox, that's why I've asked what was wrong in my<br>
> process ... right now I'm on Gmail in chrome and wayland-devel channel<br>
> and zero attachment whatsoever.<br>
<br>
</div>If you're referring to e-mail attachments that's not what he's getting<br>
at. When you apply a patch off the mailing list you literally apply the<br>
e-mail itself, not an attachment. Hence why you'd use git-am instead of<br>
git-apply. git-am takes a saved copy of the e-mail (in mbox format),<br>
extracts the inline patch for you, and applies it to the tree. It's<br>
somewhat of a different process then just applying a plain old patches.<br>
<br>
It's a very different system then most projects nowadays use, since most<br>
projects will just do pull requests and that sort of stuff :). So seeing<br>
misunderstandings like this isn't at all unusual or something to be<br>
disheartened about. We're not the only project to do it though, you'll<br>
see that the linux kernel requires you to submit patches in this manner<br>
too. It's mostly done because with organized projects like this, having<br>
the ability to easily review a patch inline is necessary to discuss<br>
changes in the protocol, point out typos and errors in patches, etc.<br>
There are alternatives for this, for example Github has the ability to<br>
allow you to comment inline on commits in pull requests, but a lot of<br>
people here just prefer to use their e-mail clients and whatever text<br>
editor they fancy.<br></blockquote><div><br></div></div></div><div>It's a really outdated system, especially considering Pipermail doesn't have an mbox link for download. My workaround is usually to hunt around for the archive on <a href="http://markmail.org" target="_blank">markmail.org</a> or <a href="http://marc.info" target="_blank">marc.info</a> and look for the mbox download, but those don't seem to be tracking wayland-devel.<br>
<br></div><div>So yeah, if you haven't subscribed to the list, hope you like copying and pasting patch files and cleaning them up to get them to apply!<br><br></div><div>(Why do we subject ourselves to this terrible infrastructure?)<br>
</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">
Hope I clarified things a bit!<br>
<br>
Cheers,<br>
Lyude<br>
<br></div><div class="">_______________________________________________<br>
wayland-devel mailing list<br>
<a href="mailto:wayland-devel@lists.freedesktop.org" target="_blank">wayland-devel@lists.freedesktop.org</a><br>
<a href="http://lists.freedesktop.org/mailman/listinfo/wayland-devel" target="_blank">http://lists.freedesktop.org/mailman/listinfo/wayland-devel</a><br>
<br></div></blockquote></div><span class="HOEnZb"><font color="#888888"><br><br clear="all"><br>-- <br> Jasper<br>
</font></span></div></div>
</blockquote></div><br></div>