-
Notifications
You must be signed in to change notification settings - Fork 308
Updated the Technical Note for WY of DPLR #562
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
phnazari
wants to merge
11
commits into
fla-org:main
Choose a base branch
from
phnazari:dplr-technical-note
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 1 commit
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
e23968f
updated the technical note for dplr
phnazari e6f1096
put the computations in the README
phnazari 8003a5f
fixed some typos
phnazari bcc35ce
Merge branch 'main' into dplr-technical-note
phnazari cfcd926
fixed latex parsing and trailing whitespace
phnazari 8385378
removed trailing whitespace
phnazari 2bf2c55
removed trailing whitespace
phnazari 7880a70
removed trailing whitespace
phnazari d957896
removed trailing white-space
phnazari a5b09ca
ran pre-commits
phnazari e1c2f2e
changed contact information
phnazari File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hosting technical documentation on Google Drive can be fragile for a public project. Links can break, access permissions might change, or the file could be deleted, making it inaccessible to future users and contributors.
For better long-term stability and to keep documentation versioned alongside the code, consider committing the technical note directly into the repository, for instance, within a
docs/directory.