Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
Tor
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Container Registry
Model registry
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
The Tor Project
Core
Tor
Commits
231564ee
Commit
231564ee
authored
8 years ago
by
J. Ryan Stinnett
Browse files
Options
Downloads
Patches
Plain Diff
Document no changes file needed for bugfixes on unreleased code
Fixes
#20932
.
parent
39f45546
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/HACKING/CodingStandards.md
+4
-0
4 additions, 0 deletions
doc/HACKING/CodingStandards.md
with
4 additions
and
0 deletions
doc/HACKING/CodingStandards.md
+
4
−
0
View file @
231564ee
...
...
@@ -93,6 +93,10 @@ What needs a changes file?
rewrites. Anything about which somebody might plausibly wonder "when
did that happen, and/or why did we do that" 6 months down the line.
What does not need a changes file?
*
Bugfixes for code that hasn't shipped in any released version of Tor
Why use changes files instead of Git commit messages?
*
Git commit messages are written for developers, not users, and they
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment