{ "version": "https://jsonfeed.org/version/1.1", "title": "chem-bla-ics", "description": "Chemblaics (pronounced chem-bla-ics) is the science that uses open science and computers to solve problems in chemistry, biochemistry and related fields.", "home_page_url": "https://chem-bla-ics.linkedchemistry.info/", "feed_url": "https://chem-bla-ics.linkedchemistry.info/2008/10/01/cherry-picking-commits-from-cdk-trunk.json", "icon": "https://chem-bla-ics.linkedchemistry.info/assets/images/chem-bla-ics_logo.png", "language": "en", "authors": [ { "name": "Egon Willighagen", "url": "https://orcid.org/0000-0001-7542-0286", "_orcid": "0000-0001-7542-0286" } ], "items": [ { "id": "https://doi.org/10.59350/6h7hy-t8615", "url": "https://chem-bla-ics.linkedchemistry.info/2008/10/01/cherry-picking-commits-from-cdk-trunk.html", "title": "Cherry-picking commits from CDK trunk: how to make a reasonable commit message", "content_html": "

Some of you heard me complain about commit messages resulting from git cherry-pick which allows me to apply patches from\nCDK trunk to a branch, without needing to do\na full merge of what happens in trunk. The commit messages would be identical, which made it seem that those original messages were mine.

\n\n

However, this is how I can modify those messages:

\n\n
$ git commit --amend\n
\n\n

This allows me to convert a mere refactored a method into Applied patch from trunk (rev 12479): [shk3] refactored a method.

", "summary": "Some of you heard me complain about commit messages resulting from git cherry-pick which allows me to apply patches from CDK trunk to a branch, without needing to do a full merge of what happens in trunk. The commit messages would be identical, which made it seem that those original messages were mine.", "date_published": "2008-10-01T00:00:00+00:00", "date_modified": "2008-10-01T00:00:00+00:00", "tags": ["git","cdk"], "authors": [ { "name": "Egon Willighagen", "url": "https://orcid.org/0000-0001-7542-0286" } ] } ] }