Issue 14077043: Let convert-ly -d reflect last effective rather than last applied rule

Keyboard Shortcuts

	File
u :	up to issue
m :	publish + mail comments
M :	edit review message
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line
<Enter> :	respond to / edit current comment
d :	mark current comment as done

	Issue
u :	up to list of issues
m :	publish + mail comments
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue
# :	close issue

	Comment/message editing
<Ctrl> + s or <Ctrl> + Enter :	save comment
<Esc> :	cancel edit

Issue 14077043: Let convert-ly -d reflect last effective rather than last applied rule (Closed)

Can't Edit
Can't Publish+Mail
Start Review

Created:
10 years, 7 months ago by dak

Modified:
10 years, 6 months ago

Reviewers:
Julien Rioux

CC:
lilypond-devel_gnu.org

Visibility:
Public.

More Reviews

Description

Let convert-ly -d reflect last effective rather than last applied rule Patchy is not really helpful for testing this one, instead one should rather do an LSR import and see where that gets.

Patch Set 1 #

Created: 10 years, 7 months ago

Download [raw] [tar.bz2]

		Unified diffs	Side-by-side diffs	Delta from patch set	Stats (+18 lines, -8 lines)			Patch
	M	Documentation/usage/updating.itely	View		1 chunk	+3 lines, -3 lines	0 comments	Download
	M	scripts/convert-ly.py	View		5 chunks	+15 lines, -5 lines	0 comments	Download

Messages

Total messages: 1

Expand All Messages | Collapse All Messages

lgtm
Cheers,
Julien

Expand All Messages | Collapse All Messages