why clustering unique reads is not support?
Closed this issue · 3 comments
y9c commented
Do you mean a incorrect merge destroy such function?
Which tools can I use to do this.
LaoZZZZZ commented
Hi Yech,
I don't quite understand your question. Would you please give me more
context?
Thank you.
Best,
Lu
…On Thu, Dec 8, 2016 at 4:42 AM, yech ***@***.***> wrote:
Do you mean a incorrect merge destroy such function?
Which tools can I use to do this.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#2>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADhw85tML1JIjyI7Go2G8PTT2xJ_OYh3ks5rF_s-gaJpZM4LHxvH>
.
--
Sincerely,
Lu
y9c commented
Bartender just tabled unique reads and did not cluster the reads.
It was caused by an incorrect merge between local branch and remote branch happened in Aug 13th 2016. It was reported by one user and was fixed at Dec 1th. I am really sorry for these fatal error introduced by this incorrect conflict resolve. Now Batender works fine.
LaoZZZZZ commented
I see. That bug has already fixed. Bartender should work fine now.
What's your use case?
…On Thu, Dec 8, 2016 at 9:47 PM, yech ***@***.***> wrote:
*Bartender just tabled unique reads and did not cluster the reads.*
It was caused by an incorrect merge between local branch and remote branch
happened in Aug 13th 2016. It was reported by one user and was fixed at Dec
1th. I am really sorry for these fatal error introduced by this incorrect
conflict resolve. Now Batender works fine.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#2 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADhw86z_IRF10_6PEVnVH0-15VaKLpoFks5rGOtcgaJpZM4LHxvH>
.
--
Sincerely,
Lu