Perhaps you should make your tags in little side branches with the direct modifications you need in them. This is what I do, take a look at one of my repos: http://github.com/tekkub/engravings/network With this users can directly download the tarball/zip directly, they don't need to know anything about git, or even that the repo *is* git.
The only issue here is that you can't use the SHA1, but honestly that always feels sorta lazy anyway. What I do is replace the version string in my code with the tag name, that's certainly more user friendly and just as easy (if not easier) to track down than a SHA1 is. On Sun, Dec 13, 2009 at 2:34 PM, Dieter_be <[email protected]>wrote: > > > On Dec 13, 2:51 am, Tekkub <[email protected]> wrote: > > If you look at the tarball that is downloaded you'll see that we give you > > the short hash. If you want the .git folder you should just clone the > repo, > > because that's created by your local git when you clone. You could also > > just hit the tag page and parse the commit off that, > http://github.com/Dieterbe/uzbl/tree/2009.11.30. There might also be a > way > > to get that info from the API. > > well.. > - short hash is not enough. i need the long one > - packaging should work without internet access > > thanks anyway > Dieter > > -- > > 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]<github%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/github?hl=en. > > > -- 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.
