On 04/11/2011 05:03 AM, Ohad Levy wrote:
git bisect is a great way to figure out which commit broke it.
Ohad
On Mon, Apr 11, 2011 at 9:45 AM, Cody Robertson <c...@hawkhost.com
<mailto:c...@hawkhost.com>> wrote:
I'll test it on more versions tomorrow to see if I can pinpoint
exactly where the change happened:
http://projects.puppetlabs.com/issues/7039
--
You received this message because you are subscribed to the Google
Groups "Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
<mailto:puppet-users@googlegroups.com>.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com
<mailto:puppet-users%2bunsubscr...@googlegroups.com>.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
--
You received this message because you are subscribed to the Google
Groups "Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
I went ahead and gave it a whirl and it appears to have done the job in
finding which commit introduced the change. Thanks for the tip!
--
Cody Robertson
1-800-859-8803 ext. 5
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
