On Fri, Jun 12, 2009 at 06:18:15PM EST, Colin Guthrie wrote:
> 'Twas brillig, and Luke Yelavich at 12/06/09 03:13 did gyre and gimble:
>
>>> So I've pushed the branch "0.9.15-branch" to my own git clone:
>>> http://colin.guthr.ie/git/pulseaudio/log/?h=0.9.15-branch
>>
>> This branch/tree appears not to have any tags, which makes it difficult to 
>> work out which commit was the last commit for the 0.9.15 release. I managed 
>> to work it out by checking the tag in the mainline pulse branch, and using 
>> that as a base to pull patches, however it seems a couple of patches do not 
>> apply cleanly. I found that commit 758aac63b97d6f5a3a6a5d74d7d0af12cd46cd3d 
>> and commit dce6af5fefbcd68d52f6ff42509213406f62c57f had hunks that failed to 
>> apply. The first patch I used was commit 
>> 4f2a3cb6019d551ca98aa2034854985df2670a30.
>>
>> Have I missed something?
>
> Oh right I forgot to push the tags... I'll do that now :) I was hoping  
> Lennart would pull the branch TBH but never mind.
>
> I'll push the v0.9.15 tag now.

The extra patches you have added to your branch do not all apply against a 
freshly downloaded and unpacked pulseaudio tarball, as I indicated in my 
previous email. I think I listed at least a couple of the commits in my last 
email, but I think there may be one more, commit 
7e664dc56a1f2ce385f6f7739209ef2413974d8f. I've tried fixing the patches, but 
the code is somewhat different for one patch, which is why it doesn't apply.

Luke
_______________________________________________
pulseaudio-discuss mailing list
[email protected]
https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss

Reply via email to