| Summary: | acerhk-0.5.26 (Bump) | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Jurek Bartuszek (RETIRED) <jurek> |
| Component: | New packages | Assignee: | No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it <maintainer-needed> |
| Status: | RESOLVED FIXED | ||
| Severity: | enhancement | CC: | mobile+disabled |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Other | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
The ebuild
The wireless keys redefinition patch |
||
|
Description
Jurek Bartuszek (RETIRED)
2005-06-13 06:56:18 UTC
Created attachment 61149 [details]
The ebuild
Created attachment 61150 [details, diff]
The wireless keys redefinition patch
Please attach your proposed changes to the ebuild as a unified diff. Hmm... I don't know if I understand you... since I've written this patch it was being accepted in every acerhk ebuild in an unchanged form. Shall I give you the output of `diff -u arg1 arg2' command? I'm not talking about the patch for acerhk.c, I'm talking about the ebuild you have attached. When submitting enhancement requests for version bumping an already existing package, it is best to attach a unified diff against the latest ebuild in portage with the changes needed for the version bump. This makes it much easier for a developer to see what changes you propose. Oh... I see... in that case, the ebuild is the same as the acerhk-0.5.22-r1.ebuild. It's just a version bump sekretarz, will you take care of this? Hmm... the 0.5.26 version is out... should I file a new bug or rename this one? Does anyone look in here anyway? We'll just update this one. Sorry about the long delay. thanks, fixed, 0.5.27 in the tree. |