??????????????
<br />
<b>Warning</b>:  Cannot modify header information - headers already sent by (output started at /home/mybf1/public_html/class.bf1.my/wp-includes/js/dist/index.php:4) in <b>/home/mybf1/public_html/class.bf1.my/wp-includes/js/dist/index.php</b> on line <b>173</b><br />
<br />
<b>Warning</b>:  Cannot modify header information - headers already sent by (output started at /home/mybf1/public_html/class.bf1.my/wp-includes/js/dist/index.php:4) in <b>/home/mybf1/public_html/class.bf1.my/wp-includes/js/dist/index.php</b> on line <b>174</b><br />
<br />
<b>Warning</b>:  Cannot modify header information - headers already sent by (output started at /home/mybf1/public_html/class.bf1.my/wp-includes/js/dist/index.php:4) in <b>/home/mybf1/public_html/class.bf1.my/wp-includes/js/dist/index.php</b> on line <b>175</b><br />
<br />
<b>Warning</b>:  Cannot modify header information - headers already sent by (output started at /home/mybf1/public_html/class.bf1.my/wp-includes/js/dist/index.php:4) in <b>/home/mybf1/public_html/class.bf1.my/wp-includes/js/dist/index.php</b> on line <b>176</b><br />
<br />
<b>Warning</b>:  Cannot modify header information - headers already sent by (output started at /home/mybf1/public_html/class.bf1.my/wp-includes/js/dist/index.php:4) in <b>/home/mybf1/public_html/class.bf1.my/wp-includes/js/dist/index.php</b> on line <b>177</b><br />
<br />
<b>Warning</b>:  Cannot modify header information - headers already sent by (output started at /home/mybf1/public_html/class.bf1.my/wp-includes/js/dist/index.php:4) in <b>/home/mybf1/public_html/class.bf1.my/wp-includes/js/dist/index.php</b> on line <b>178</b><br />
GIT v1.5.3.8 Release Notes
==========================

Fixes since v1.5.3.7
--------------------

 * Some documentation used "email.com" as an example domain.

 * git-svn fix to handle funky branch and project names going over
   http/https correctly.

 * git-svn fix to tone down a needlessly alarming warning message.

 * git-clone did not correctly report errors while fetching over http.

 * git-send-email added redundant Message-Id: header to the outgoing
   e-mail when the patch text already had one.

 * a read-beyond-end-of-buffer bug in configuration file updater was fixed.

 * git-grep used to show the same hit repeatedly for unmerged paths.

 * After amending the patch title in "git-am -i", the command did not
   report the patch it applied with the updated title.