chromium_src.git - central chromium sources

	Commit message (Collapse)	Author	Age	Files	Lines
*	Updated usrsctp in DEPS.	lally@chromium.org	2013-11-22	1	-1/+1
\| \| \| \| \| \| \| \| \| \| \| \|	Enable SCTP on Android. BUG= TESTED=Yes, by hand. RISK=P1 Review URL: https://codereview.chromium.org/75733004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@236662 0039d316-1c4b-4281-b951-d872f2087c98
*	Updated usrsctp to latest version (to 8603) with fixes upstream. Fixed ↵	ldixon@google.com	2013-09-06	8	-1817/+34
\| \| \| \| \| \| \| \| \| \|	usrsctp gyp file; removed overides. usrsctp update = 8554:8603 Review URL: https://chromiumcodereview.appspot.com/23960004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@221656 0039d316-1c4b-4281-b951-d872f2087c98
*	Updated usrsctp to fix various issues for windows (using changes pushed ↵	ldixon@google.com	2013-08-06	7	-106/+216
\| \| \| \| \| \| \| \| \| \| \| \| \| \|	upstream) and unified SHA1 treatment with libjingle. Note: HAVE_SCTP is still currently turned off for windows (while investigating an apparent issue in win xp) (patch from issue 19522005; exactly the same, except HAVE_SCTP is not turned on for windows) BUG= Review URL: https://chromiumcodereview.appspot.com/21968004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@215983 0039d316-1c4b-4281-b951-d872f2087c98
*	Revert 215206 "This fixes bugs in windows that Lally got upstrea..."	toyoshim@chromium.org	2013-08-02	7	-216/+106
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	As ckocagil@chromium.org suggested in IRC, I try reverting this to fix the XP bots failures. > This fixes bugs in windows that Lally got upstream in usrsctp. This now enables the HAVE_SCTP flag for windows. > > BUG= > > Review URL: https://chromiumcodereview.appspot.com/19522005 TBR=ldixon@google.com, ckocagil@chromium.org Review URL: https://codereview.chromium.org/21743002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@215239 0039d316-1c4b-4281-b951-d872f2087c98
*	This fixes bugs in windows that Lally got upstream in usrsctp. This now ↵	ldixon@google.com	2013-08-02	7	-106/+216
\| \| \| \| \| \| \| \| \| \|	enables the HAVE_SCTP flag for windows. BUG= Review URL: https://chromiumcodereview.appspot.com/19522005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@215206 0039d316-1c4b-4281-b951-d872f2087c98
*	Enable SCTP target in libjingle.gyp. SCTP was already existed in Chrome ↵	mallinath@chromium.org	2013-06-12	11	-27/+2173
\| \| \| \| \| \| \| \|	third_party for a while but never used. Libjingle is trying use it for DataChannels. Review URL: https://chromiumcodereview.appspot.com/16196007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@205864 0039d316-1c4b-4281-b951-d872f2087c98
*	Initial addition of usrsctp.	ldixon@google.com	2013-05-08	3	-0/+142
	About to become a dependency for LibJingle's WebRTC reliable data channels. (Note: have already got git and svn repositories setup, and open-source approval from: https://codereview.chromium.org/12779026/ but I accentually created that CL/issue from a client without commit access, on a different machine. I don't know how to update that CL from my new git checkout of chromium...) BUG=238870 TEST=none Review URL: https://chromiumcodereview.appspot.com/14453006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@198908 0039d316-1c4b-4281-b951-d872f2087c98