Bob Copeland wrote: > On Fri, Aug 1, 2008 at 11:02 AM, Jiri Slaby <[EMAIL PROTECTED]> wrote: > >>> Not to worry, the commit that introduced it was >>> 9d139c810a2aa17365cc548d0cd2a189d8433c65, which as far as I can tell >>> came in after 2.6.26. >>> >> git-describe 9d139c810a2aa17365cc548d0cd2a189d8433c65 >> v2.6.26-rc8-1219-g9d139c8 >> > > I'm not that expert in git, what does that mean? Some other commits > for 2.6.27 also show a 2.6.26-rc from git-describe (e.g. my > 3a078876caee). > > For my own investigation, I did a 'git-checkout v2.6.26' and looked at > the code to see the patch had not been applied yet. Is there an > easier way to definitively say commit X is/is not in tagged release Y? > >
Aha! I think we want git-describe --contains. $ git-describe --contains 2b142900784c6e38c8d39fa57d5f95ef08e735d8 v2.6.27-rc1~55^2~1 Alan _______________________________________________ ath5k-devel mailing list ath5k-devel@lists.ath5k.org https://lists.ath5k.org/mailman/listinfo/ath5k-devel
