On Mon, Mar 17, 2014 at 8:51 AM, Nguyễn Thái Ngọc Duy <pclo...@gmail.com> wrote: > Signed-off-by: Nguyễn Thái Ngọc Duy <pclo...@gmail.com> > --- > v2 renames the option name to --nonlinear-barrier and fixes using it > with --dense. Best used with --no-merges to see patch series. > > Documentation/rev-list-options.txt | 7 ++++++ > log-tree.c | 4 +++ > revision.c | 51 > +++++++++++++++++++++++++++++++++++--- > revision.h | 6 +++++ > 4 files changed, 65 insertions(+), 3 deletions(-) > > diff --git a/Documentation/rev-list-options.txt > b/Documentation/rev-list-options.txt > index 03533af..435aa2d 100644 > --- a/Documentation/rev-list-options.txt > +++ b/Documentation/rev-list-options.txt > @@ -750,6 +750,13 @@ This enables parent rewriting, see 'History > Simplification' below. > This implies the `--topo-order` option by default, but the > `--date-order` option may also be specified. > > +--nonlinear-barrier[=<barrier>]:: > + When --graph is not used, all history branches are flatten and
s/flatten/flattened/ > + could be hard to see that the two consecutive commits do not s/and could be/which can make it/ > + belong to a linear branch. This option puts a barrier in > + between them in that case. If `<barrier>` is specified, it > + is the string that will be shown instead of the default one. > + > ifdef::git-rev-list[] > --count:: > Print a number stating how many commits would have been -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
