5 Commits

Author	SHA1	Message	Date
Sebastiaan van Stijn	cc35939485	Revert "Require continuation char to be last char in a line" ... This reverts commit 105bc63295a7126798d3722a0e205c5ead4e2b1c, which (although correct), resulted in a backward incompatible change. We can re-implement this in future, after this changes goes through a deprecation cycle Signed-off-by: Sebastiaan van Stijn <github@gone.nl> Upstream-commit: c67550414b762ab32ea3e9645ebcafb79cb9059d Component: engine	2017-01-10 00:41:03 +01:00
Vincent Demeester	e8c489744e	Revert "Fix dockerfile parser with empty line after escape" ... This reverts commit 3e1b539e8d0ed4abf695b0a8c42346fba6d5a6b0. Signed-off-by: Vincent Demeester <vincent@sbr.pm> Upstream-commit: 6e0666e622a8b1fc19c19eb490d218eebca15edc Component: engine	2016-12-02 14:15:55 +01:00
Yong Tang	bad2fec338	Fix dockerfile parser with empty line after escape ... This fix tries to fix the bug reported by #24693 where an empty line after escape will not be stopped by the parser. This fix addresses this issue by stop the parser from continue with an empty line after escape. An additional integration test has been added. This fix fixes #24693. Signed-off-by: Yong Tang <yong.tang.github@outlook.com> Upstream-commit: 3e1b539e8d0ed4abf695b0a8c42346fba6d5a6b0 Component: engine	2016-10-27 10:43:08 -07:00
Doug Davis	5bbd3d9214	Require continuation char to be last char in a line ... While look at #27039 I noticed that we allow for whitespace after the continuation char (\\) which is wrong. It needs to be the very last char in the line. Signed-off-by: Doug Davis <dug@us.ibm.com> Upstream-commit: 105bc63295a7126798d3722a0e205c5ead4e2b1c Component: engine	2016-10-04 09:38:00 -07:00
Tibor Vass	5d2ec8fed8	Move builder files to builder/dockerfile ... Signed-off-by: Tibor Vass <tibor@docker.com> Upstream-commit: f41230b93a77ca7f4d84718f39a4847b6117f694 Component: engine	2015-10-05 18:26:47 -04:00