<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Sat, Jun 22, 2013 at 7:54 PM, Jean-Yves Avenard <span dir="ltr"><<a href="mailto:jyavenard@gmail.com" target="_blank">jyavenard@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
Not sure I understand that gentoo business, why would you need to have<br>
separate patches for standard fixes/0.26 commits...<br>
<br>
Thanks<br>
<span class=""><font color="#888888">JY</font></span><br></blockquote><div><br></div><div>Through the epatch-user function, Gentoo allows you to apply package- and/or version- specific patches without having to modify the standard ebuild script for the package. In the default configuration, the epatch-user picks up files with the extension .patch in /etc/portage/patches/<category>/<package name> and applies them in alphabetical order. The standard patchset the OP was talking about is just the way that Gentoo has chosen to package the -fixes patchset. I think they use git-format-patch against the base release version to create a series of patches (one per commit) for the relevant -fixes branch. That saves bandwidth so users don't need to re-download the entire source tarball for a new -fixes version, only the updated patches archive.<br>
<br></div><div>Sorry if my reply was a bit long-winded, but I only recently learned about the epatch-user function myself, and I expect other Gentoo users might find it useful. That's one reason why I like Gentoo--it's super easy to apply patches to test or fix something.<br>
<br></div><div>Sincerely,<br><br>Karl<br></div></div></div></div>