I have a pointer to the latest commit on the remote/master that I rebased to before starting work. I didn't check to see if there was a new commit in the meanwhile (oops...) - I will do so in the future before pushing. 

Matt Massie <notifications@github.com> wrote:

>>        builder.setRecordGroupId(recordGroup.getReadGroupId)
>> -        .setRecordGroupSequencingCenter(recordGroup.getSequencingCenter)
>
>Looks like this pull request isn't based on the latest master commit (d4b9200c5f960f6a8e9b5f45624770f8d2b6d834). I'm pretty sure this won't be an issue... and will drop away when this request is merged into master. In the future, the pull request will be a little cleaner if you `git fetch origin && git rebase origin/master` on your feature branch before creating the pull request.
>
>---
>Reply to this email directly or view it on GitHub:
>https://github.com/massie/adam/pull/5/files#r6789898<p>In adam-commands/src/main/scala/edu/berkeley/cs/amplab/adam/commands/Bam2Adam.scala:</p>
><pre style='color:#555'>&gt;        builder.setRecordGroupId(recordGroup.getReadGroupId)
>&gt; -        .setRecordGroupSequencingCenter(recordGroup.getSequencingCenter)
></pre>
><p>Looks like this pull request isn't based on the latest master commit (<a href="https://github.com/massie/adam/commit/d4b9200c5f960f6a8e9b5f45624770f8d2b6d834" class="commit-link"><tt>d4b9200</tt></a>). I'm pretty sure this won't be an issue... and will drop away when this request is merged into master. In the future, the pull request will be a little cleaner if you <code>git fetch origin &amp;&amp; git rebase origin/master</code> on your feature branch before creating the pull request.</p>
>
><p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">&mdash;<br>Reply to this email directly or <a href='https://github.com/massie/adam/pull/5/files#r6789898'>view it on GitHub</a>.<img src='https://github.com/notifications/beacon/fIZLoLkaei-JI9T-ls2Mx5xWPAPP4SIlmtkg8ySCnVNvL5AbPiEPuk_WwaA51U0d.gif' height='1' width='1'></p>