Don't create a time signature by default when time signatures are present

[craffel]

Don't create a time signature by default when time signatures are present

[craffel]

@douglaseck if this is solved in be70895 can you close? Thanks.

[douglaseck]

I tried by doing this:
git commit --amend -m "Add a comparator for sorting a track that handles
all event types. Fixes #61"
git pull
git push origin master

So I think that put "Fixes 61" in the commit message.

Git is becoming less magical as I use it, but the less magical it becomes,
the more I'm somewhat annoyed by it. I'm sure I'll learn. There's got to be
a good reason it took over the world. There's got to be a reason you can't
just close an open issue by clicking "Close" somewhere on the issue . ..

On Tue, May 10, 2016 at 2:16 PM, Colin Raffel [email protected]
wrote:

@douglaseck https://github.com/douglaseck if this is solved in be70895
be70895
can you close? Thanks.

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#61 (comment)

[craffel]

So, that would work on your own fork; you can only push commits to your fork of pretty-midi, not my fork. There is indeed a "close" button, it's next to the "comment" button on the issues page:
#61
You are getting me curious as to how they do things internally at Google...

[douglaseck]

But I think that close button only shows up for the owner of the issue. See
attached screenshot of what I see.

On Tue, May 10, 2016 at 3:59 PM, Colin Raffel [email protected]
wrote:

So, that would work on your own fork; you can only push commits to your
fork of pretty-midi, not my fork. There is indeed a "close" button, it's
next to the "comment" button on the issues page:
#61 #61
You are getting me curious as to how they do things internally at Google...

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#61 (comment)

[craffel]

Oops, sorry, I had thought you had opened this issue (you just reported it). I'll close it!

[douglaseck]

So git/github is not all that crazy after all :-)

On Tue, May 10, 2016 at 5:04 PM, Colin Raffel [email protected]
wrote:

Oops, sorry, I had thought you had opened this issue (you just reported
it). I'll close it!

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#61 (comment)

[craffel]

Haha, yeah, just me...