-
Notifications
You must be signed in to change notification settings - Fork 11
Commit messages of the rewrite #22
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
Comments
How do I add the messages to commits that already exist? |
On Thu, Jun 09, 2022 at 03:53:00PM -0700, lord-ne wrote:
How do I add the messages to commits that already exist?
I can do that. (It will be done outside "github.com".)
It is the text that this issue should yield. Paste them here.
Groeten
Geert Stappers
--
Silence is hard to parse
|
Here is the commit message for the first commit (Add delay_count and delay_loop internal functions):
Here is the commit message for the second commit (Implement delay, delay_ms, and delay_us):
Here is the commit message for the third commit (Divide numerator and denominator by their GCD at compile time):
|
Those commit message are now at http://uta.stappers.it/git/avr-rust/delay in branch
to get them. File #[cfg(test)]
mod tests {
#[test]
fn it_works() {
assert_eq!(2 + 2, 4);
}
} For those who like to remove that @lord-ne if you want the "rewrite changes", that originate from #17, merged, make a merge request so we can discuss this further. Branch |
I created the pull request, so I think this issue can be closed now |
Rewrite: Prevent overflow from public functions Hopefully are the underlaying commits preserved. Yes, I do fear that "github.com" does `git merge --squash`. What "lord-ne" wrote: This is the rewrite discussed in #17. Its main purpose is to ensure that public functions cannot overflow, by having them delegate to private functions that accept larger parameters. Some work was also put in to mitigating the effects of the delays not being inlined at compile time. Additional a link to #22 are is being asked for good commit messages.
merged (now closing the issue) |
In #17 are many things discussed. None of that information is in branch
rewrite
. That shouldn't be.Have look at https://github.com/ipxe/ipxe/commits for examples of good commit messages.
Thing I'm asking for is commit messages, not only commit summaries.
Rule of thumb: More than one line.
Please provide the missing messages for branch
rewrite
.The text was updated successfully, but these errors were encountered: