Go to file
Marcus Holl 7ba3995c3a Fix documentation for merge strategy 'fast-forward-only'
The documentation for merge strategy 'fast-forward-only' asserts that
fast-forward-only produces a strictly linear history. But even with
fast-forward-only it is possible to produce histories not being strictly
linear. E.g. some predecessors of the change being pushed might be
merge commits. The point is that by submitting a change no merge
commit will be created when merge strategy is fast-forward-only.

Change-Id: Ia68e6bac7fb49b1398971e7a23d4277f1ca51b06
2014-12-19 00:43:16 +00:00
2014-11-08 08:31:08 -08:00
2014-12-04 11:23:01 +09:00
2014-12-10 12:49:26 +09:00
2013-11-30 01:53:00 -08:00
2014-12-08 09:48:09 +09:00
2014-12-08 09:48:09 +09:00
2014-12-10 12:49:26 +09:00
2014-12-08 09:48:09 +09:00
2014-11-05 09:46:58 +09:00
2014-12-12 20:25:48 +09:00
2014-12-04 11:23:01 +09:00
2014-12-17 22:41:02 +01:00
2014-11-08 08:31:08 -08:00
2013-11-09 07:45:00 +01:00
2014-11-06 09:15:44 +01:00
2014-05-19 11:41:31 -07:00
2008-11-14 16:59:34 -08:00
2009-03-27 20:20:10 -07:00
2014-12-08 09:48:09 +09:00
Description
RETIRED, Gerrit as used by OpenStack
120 MiB