[pacman-dev] [GIT] The official pacman repository branch, master, updated. v3.2.2-93-g2268981

[Dan McGee]

On Mon, Feb 23, 2009 at 8:53 PM, Bryan Ischo
<bji-keyword-pacman.3644cb at www.ischo.com> wrote:
> Dan McGee wrote:
>>
>> This is an automated email from the git hooks/post-receive script. It was
>> generated because a ref change was pushed to the repository containing
>> the project "The official pacman repository".
>>
>> The branch, master has been updated
>>       via  2268981ebf562a7dda1e788dbd931e48adf9fabb (commit)
>>       via  9d661240fe77127fbede95066f38f12cad598e2d (commit)
>>       via  f57f8d33862050acc8d131710c100ba47877e675 (commit)
>>       via  02685504012a4880e599b15f1060f6bd0bf48797 (commit)
>>       via  a309a016bfed9f67452f2a6556fb4391fd55b34e (commit)
>>       via  c8a41b7d6da7f820754a07cb085687ea5e110f85 (commit)
>>       via  c590ac0997b5c82ddf9115191e9ac5c79efde227 (commit)
>>      from  1c4633ea2cbc01cfd7929509724951615827c482 (commit)
>>
>> Those revisions listed above that are new to this repository have
>> not appeared on any other notification email; so we list those
>> revisions in full, below.
>>
>
>
> Thank you for taking my patches, and thanks for fixing the whitespace issues
> therein.
>
> My patches fix bug 9395; should I post in that bug noting such?  Or should I
> wait until a version of pacman is released to the public that includes these
> changes?

Post a comment for sure, pointing out the commit sha1s. I'll mark it
as due in 3.3.

RE: library version numbers- we always bump them on a .X release, so
no worries there. We had already changed the library signature anyway.

-Dan