This is an automated email from the ASF dual-hosted git repository.
arm pushed a change to branch moving_file_ui_to_compose
in repository https://gitbox.apache.org/repos/asf/tooling-trusted-releases.git
omit 984a55a4 #931 - tidy up file planner code
omit df3abbc7 #435 - add hint that entering a new directory name will
create it
omit 992033f4 #931 - moving file planner to compose phase
add 692f7790 #919 - remove action buttons from committee page for
non-members/admins
add ec2a4c1d #931 - moving file planner to compose phase
add 4c89556b #435 - add hint that entering a new directory name will
create it
add 574295b6 #931 - tidy up file planner code
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (984a55a4)
\
N -- N -- N refs/heads/moving_file_ui_to_compose (574295b6)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
atr/get/committees.py | 6 +++++-
atr/templates/committee-view.html | 21 +++++++++++++--------
atr/web.py | 9 ++++++---
3 files changed, 24 insertions(+), 12 deletions(-)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
