On Mon, Apr 26, 2010 at 3:33 PM, Kyle Neath <[email protected]> wrote:
> We'll take it into advisement, but it's extremely unlikely we'll do any
> regex magic to strip things from tag names.

I'm not a paying github customer, so I know I have no right to expect
anybody to implement features for me, or for that matter, to even
reply to my emails.  So I'm quite impressed that you're replying at
all.  However, I'm not sure why you've bothered to reply to this
thread if you don't want to have a legitimate discussion.

What is the benefit of the current file naming scheme?  Who does it help?

Who are these people that don't have git, but don't use the release
tarballs, and thus require poorly-named non-release tarballs of
intermediate releases?  Why would these people object to having the
names be cleaned up instead of filled with >50% redundant characters?

As far as I can see, it's in github's best interest to have developers
(such as me) start to rely on it github as a fundamental part of their
release process.  Right now, my releases involve:

1) make a tag
2) make a tarball
3) upload a tarball somewhere
4) update a file index to point at that tarball

If the github tarballs were useful, it could be reduced to:

1) make a tag

That would be *awesome*, and it would make me that much more reliant
on github, so that when you inevitably start charging for (or adding
advertising or whatever) this awesome service I'm currently getting
for free, software maintainers like me would be that much more likely
to stick around rather than migrating to some other provider.  And I
can't possibly be the only one in this position.

Thanks,

Avery

P.S. Everyone knows that "We'll take it under advisement" is secret
code for "shut up and go away."  It would be more honest, and would
save us a lot of time, if you had just said that instead.

-- 
You received this message because you are subscribed to the Google Groups 
"GitHub" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/github?hl=en.

Reply via email to