tagging github commits as releases? about eb-garamond HOT 5 CLOSED

Ah, ok, now I understand what those tags are good for. Of course I can do so (now that they make sense to me :)). But does it make sense to have all the html files in the source tarball too? What’s more, there’s a "build" folder which I stopped updating some releases back, including that wouldn’t make much sense neither, would it?

from eb-garamond.

You can run "make clean" to at least clean out the build folder. html might
be ok to include, it's documentation in a way. The alternative is to host
the website in another repo, but it might not be that big of deal either
way.

On Wed, Jun 5, 2013 at 7:24 PM, georgd [email protected] wrote:

Ah, ok, now I understand what those tags are good for. Of course I can do
so (now that they make sense to me :)). But does it make sense to have all
the html files in the source tarball too? What’s more, there’s a "build"
folder which I stopped updating some releases back, including that wouldn’t
make much sense neither, would it?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/42#issuecomment-19015813
.

from eb-garamond.

Of course. But you don’t suggest to try to change ancient commits this way?

from eb-garamond.

There's no need to change things in the past; this is something to keep in
mind going forward. By the way, thanks for the font. It's beautiful and one
of my favorite!

On Thu, Jun 6, 2013 at 4:36 AM, georgd [email protected] wrote:

Of course. But you don’t suggest to try to change ancient commits this way?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/42#issuecomment-19031686
.

from eb-garamond.

I’ll do so in the future, thus closing this report.

from eb-garamond.