Lines Matching +full:- +full:- +full:no +full:- +full:git +full:- +full:commit
1 <!--
4 SPDX-License-Identifier: curl
5 -->
59 changes](https://curl.se/dev/sourceactivity.html) in git. Just lurking on the
60 [curl-library mailing list](https://curl.se/mail/list.cgi?list=curl-library)
69 [CODE_STYLE](https://curl.se/dev/code-style.html) already established in
75 ### Non-clobbering All Over
87 odd problems, but discussions and opinions do not agree with 510 of them - or
92 Preferably, each fix that corrects a problem should be in its own patch/commit
93 with its own description/commit message stating exactly what they correct so
104 the most up-to-date sources from the git repository, but the latest release
138 patch to [the curl-library mailing
139 list](https://curl.se/mail/list.cgi?list=curl-library).
163 git commit that is easy to merge and they are easy to track and not that easy
175 You can update your pull requests by pushing new commits or force-pushing
176 changes to existing commits. Force-pushing an amended commit without any
177 actual content changed also allows you to retrigger the tests for that commit.
182 A pull request sent to the project might get labeled `needs-votes` by a
186 form of messages saying so, or thumbs-up reactions on GitHub.
196 ### Commit messages
198 A short guide to how to write git commit messages in the curl project.
200 ---- start ----
202 -- empty line --
203 [full description, no wider than 72 columns that describes as much as
207 -- empty line --
208 [[0] URL - Reference to a URL in the description, almost like Markdown;
209 the last numbered reference is followed by an -- empty line -- ]
210 [Follow-up to {shorthash} - if this fixes or continues a previous commit;
211 add a Ref: that commit's PR or issue if it's not a small, obvious fix;
212 followed by an -- empty line -- ]
215 [Approved-by: John Doe - credit someone who approved the PR; if you are
216 committing this for someone else using --author=... you do not need this
218 [Authored-by: John Doe - credit the original author of the code; only use
219 this if you cannot use "git commit --author=..."]
220 [Signed-off-by: John Doe - we do not use this, but do not bother removing it]
221 [whatever-else-by: credit all helpers, finders, doers; try to use one of
223 Acked-by:, Assisted-by:, Co-authored-by:, Found-by:, Reported-by:,
224 Reviewed-by:, Suggested-by:, Tested-by:]
225 [Ref: #1234 - if this is related to a GitHub issue or PR, possibly one that
227 [Ref: URL to more information about the commit; use Bug: instead for
229 [Fixes #1234 - if this closes a GitHub issue; GitHub closes the issue once
230 this commit is merged]
231 [Closes #1234 - if this closes a GitHub PR; GitHub closes the PR once this
232 commit is merged]
233 ---- stop ----
237 - use the imperative, present tense: "change" not "changed" nor "changes"
238 - do not capitalize the first letter
239 - no period (.) at the end
242 similar. There is no fixed list to select from but using the same "area" as
245 Do not forget to use commit --author=... if you commit someone else's work, and
246 make sure that you have your own user and email setup correctly in git before
247 you commit.
250 than one person was involved. There is no need to credit yourself unless you
251 are using --author=... which hides your identity. Do not include people's
253 a previous commit; saying `{userid} on github` is OK.
255 ### Write Access to git Repository
257 If you are a frequent contributor, you may be given push access to the git
258 repository and then you are able to push your changes straight into the git
264 ### How To Make a Patch with git
268 git clone https://github.com/curl/curl.git
270 You then proceed and edit all the files you like and you commit them to your
273 git commit [file]
275 As usual, group your commits so that you commit all changes at once that
281 git format-patch remotes/origin/master
283 This creates files in your local directory named `NNNN-[name].patch` for each
284 commit.
286 Now send those patches off to the curl-library list. You can of course opt to
287 do that with the 'git send-email' command.
289 ### How To Make a Patch without git
297 diff -u unmodified-file.c my-changed-one.c > my-fixes.diff
302 diff -ur curl-original-dir curl-modified-sources-dir > my-fixes.diff
308 - [Webinar on getting code into cURL](https://www.youtube.com/watch?v=QmZ3W1d6LQI)
313 request and commit to verify that the *REUSE state* of all files are still
318 the SPDX-License-Identifier included. If the header does not work, you can use a
323 `./scripts/copyright.pl` script in the root of the git repository.