##// END OF EJS Templates
filemerge: be more strict when detecting conflict markers, add `|` markers...
filemerge: be more strict when detecting conflict markers, add `|` markers I received a user complaint about detecting a line that contained 78 `=` followed by `*/` as a conflict marker. We'll never generate that, we generate 7 identical characters and either the end of the line, or a space. Let's be explicit about detecting exactly what we produce to reduce the chances of a false positive. While we're here, add `|||||||` as a detected conflict marker (generated with the `keep-merge3` style conflicts). Differential Revision: https://phab.mercurial-scm.org/D11391

File last commit:

r45237:a347a329 default
r48753:053dd53a stable
Show More
lib.rs
15 lines | 383 B | application/rls-services+xml | RustLexer
// Copyright 2018 Yuya Nishihara <yuya@tcha.org>
//
// This software may be used and distributed according to the terms of the
// GNU General Public License version 2 or any later version.
mod attachio;
mod clientext;
pub mod locator;
pub mod message;
pub mod procutil;
mod runcommand;
mod uihandler;
pub use clientext::ChgClient;
pub use uihandler::{ChgUiHandler, SystemHandler};