Good point, I should have thought of the revision history myself. Thanks! On Mon, Oct 20, 2014 at 6:16 AM, Rob McBroom <[email protected]> wrote:
> On 19 Oct 2014, at 17:30, David Rees wrote: > > For those of us beta testing it sure would be helpful if the release notes >> were organized by beta release (400F, 400E, etc) so we could see what just >> changed (so we know what to test). Then you could just combine them into >> one when you release. >> > > I know what you mean, but the release notes are embedded into the app and > we usually don’t know which one is going to end up as the final release. > That is, if we had released 400E and everything looked fine, we would have > just made it final and everyone would have gotten it (unchanged). > > This is probably as close as you can get to what you’re asking for: > > https://github.com/quicksilver/Quicksilver/compare/build400E...build400F > > -- > Rob McBroom > http://www.skurfer.com/ > > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Quicksilver" group. > To unsubscribe from this topic, visit https://groups.google.com/d/ > topic/blacktree-quicksilver/I96D4xa83Zw/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To post to this group, send email to blacktree-quicksilver@ > googlegroups.com. > Visit this group at http://groups.google.com/group/blacktree-quicksilver. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Quicksilver" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/blacktree-quicksilver. For more options, visit https://groups.google.com/d/optout.
