Not really, no; it is probably worth doing though. If you can trust me, the latest version should always be the latest commit in master. The build gets raised about 5 minutes after a commit, so unless the build is failing (which it isn't: http://teamcity.codebetter.com/viewType.html?buildTypeId=bt9&tab=buildTypeStatusDiv) it will always be the latest.
I shall try to think of a way to incorporate the commit id into the source. On Tue, Jan 19, 2010 at 3:17 PM, Fost andy <[email protected]> wrote: > Hi, > > Apologies for what is probably a very mundane question but I am not > that familiar with this scale of version control, git or github. > > Is there an easy way to link up the binaries produced on the fluent- > nhibernate page (currently at 614) with the github commits (currently > at 89c7525e8db68ca5e558ffb80fd16983eacf8b03)? > > cheers, > Andy > > -- > You received this message because you are subscribed to the Google Groups > "Fluent NHibernate" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<fluent-nhibernate%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/fluent-nhibernate?hl=en. > > > >--
You received this message because you are subscribed to the Google Groups "Fluent NHibernate" 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/fluent-nhibernate?hl=en.
