Fri, 08 Aug 2014 23:15:26 -0700 pkg: prepare release 4.1.0 stable 4.1.0
Pierre-Yves David <pierre-yves.david@fb.com> [Fri, 08 Aug 2014 23:15:26 -0700] rev 1049
pkg: prepare release 4.1.0
Fri, 08 Aug 2014 23:14:00 -0700 merge default into stable stable
Pierre-Yves David <pierre-yves.david@fb.com> [Fri, 08 Aug 2014 23:14:00 -0700] rev 1048
merge default into stable Release 4.1.0 is coming
Fri, 08 Aug 2014 23:02:26 -0700 evolve: adds a --confirm option
Pierre-Yves David <pierre-yves.david@fb.com> [Fri, 08 Aug 2014 23:02:26 -0700] rev 1047
evolve: adds a --confirm option This option lets the use double check if it wants the evolve operation.
Fri, 08 Aug 2014 23:11:09 -0700 evolve: gather evolve output together
Pierre-Yves David <pierre-yves.david@fb.com> [Fri, 08 Aug 2014 23:11:09 -0700] rev 1046
evolve: gather evolve output together We stop relying on ui.status being muted when --quiet is used. Instead we use plain write and hide this behind an explicite ui.quiet check. This will help use enforcing this output in the comming --confirm mode.
Fri, 08 Aug 2014 21:06:48 -0700 doc: forgotten amend
Pierre-Yves David <pierre-yves.david@fb.com> [Fri, 08 Aug 2014 21:06:48 -0700] rev 1045
doc: forgotten amend
Thu, 12 Jun 2014 14:41:13 -0700 evolve: attempt to clarify the documentation around --all and --any
Pierre-Yves David <pierre-yves.david@fb.com> [Thu, 12 Jun 2014 14:41:13 -0700] rev 1044
evolve: attempt to clarify the documentation around --all and --any This have been confusing to people. We try to be a bit more verbose in the evolve help.
Fri, 08 Aug 2014 18:15:01 -0700 evolve: re enable progress for all
Pierre-Yves David <pierre-yves.david@fb.com> [Fri, 08 Aug 2014 18:15:01 -0700] rev 1043
evolve: re enable progress for all Progress is an important information for user facing slow push.
Fri, 08 Aug 2014 18:06:08 -0700 evolve: stop pretending we are pulling markers when we don't
Pierre-Yves David <pierre-yves.david@fb.com> [Fri, 08 Aug 2014 18:06:08 -0700] rev 1042
evolve: stop pretending we are pulling markers when we don't If discovery did not found any unknown marker, we should not display the "pulling marker" message.
Fri, 08 Aug 2014 18:01:02 -0700 evolve: do not even try to pull if all remote markers are known
Pierre-Yves David <pierre-yves.david@fb.com> [Fri, 08 Aug 2014 18:01:02 -0700] rev 1041
evolve: do not even try to pull if all remote markers are known previously we were explicitly pulling an empty bundle.
Fri, 08 Aug 2014 17:49:22 -0700 evolve: add "obsolescence" in front of marked in the previous message
Pierre-Yves David <pierre-yves.david@fb.com> [Fri, 08 Aug 2014 17:49:22 -0700] rev 1040
evolve: add "obsolescence" in front of marked in the previous message
Fri, 08 Aug 2014 17:46:20 -0700 evolve: make the "X markers added" message during pull important
Pierre-Yves David <pierre-yves.david@fb.com> [Fri, 08 Aug 2014 17:46:20 -0700] rev 1039
evolve: make the "X markers added" message during pull important
Fri, 08 Aug 2014 17:40:01 -0700 evolve: make the "pulling obsolescence marker" message important
Pierre-Yves David <pierre-yves.david@fb.com> [Fri, 08 Aug 2014 17:40:01 -0700] rev 1038
evolve: make the "pulling obsolescence marker" message important This is likely to take some time the user needs to know what is going on.
Fri, 08 Aug 2014 17:34:22 -0700 evolve: add "absolescence" in front of markers in the message
Pierre-Yves David <pierre-yves.david@fb.com> [Fri, 08 Aug 2014 17:34:22 -0700] rev 1037
evolve: add "absolescence" in front of markers in the message
Fri, 08 Aug 2014 17:29:29 -0700 evolve: re-introduce the "pushing 42 markers…" message
Pierre-Yves David <pierre-yves.david@fb.com> [Fri, 08 Aug 2014 17:29:29 -0700] rev 1036
evolve: re-introduce the "pushing 42 markers…" message Informing the user about marker behind pushed sounds a good idea.
Fri, 08 Aug 2014 17:16:29 -0700 evolve: hide the OBSEXC message behind a config option
Pierre-Yves David <pierre-yves.david@fb.com> [Fri, 08 Aug 2014 17:16:29 -0700] rev 1035
evolve: hide the OBSEXC message behind a config option This will lets most people ignore them while keep evolve dev having a close look at them. Some of the most useful messages will be reintroduced for all in coming changeset.
Fri, 08 Aug 2014 17:10:31 -0700 evolve: move OBSEXC progress in a dedicated function
Pierre-Yves David <pierre-yves.david@fb.com> [Fri, 08 Aug 2014 17:10:31 -0700] rev 1034
evolve: move OBSEXC progress in a dedicated function This will help use to rework them.
(0) -1000 -300 -100 -16 +16 +100 +300 +1000 +3000 tip