Luke-Jr [ARCHIVE] on Nostr: 📅 Original date posted:2011-12-21 🗒️ Summary of this message: Mike Hearn asks ...
📅 Original date posted:2011-12-21
🗒️ Summary of this message: Mike Hearn asks if there is a way to improve Git's summaries for merge commits. Suggestion given to use `git log --no-merges`.
📝 Original message:On Wednesday, December 21, 2011 5:12:07 AM Mike Hearn wrote:
> Git does not produce very helpful summaries when every commit is a merge.
> Is there a way to fix that? You have to guess what a change does based on
> the name of the topic branch currently.
Not sure what you mean. Maybe `git log --no-merges` ?
Published at
2023-06-07 02:52:11Event JSON
{
"id": "15c3e62dd99295867c4e8776da4f2c1fc18c50e5e54e2b278429bf53c42b6c7e",
"pubkey": "6ac6a519b554d8ff726a301e3daec0b489f443793778feccc6ea7a536f7354f1",
"created_at": 1686106331,
"kind": 1,
"tags": [
[
"e",
"924d5213d8a8718a2931f8a3d7e4389210af618017997f4d36bda53f53d55ca6",
"",
"root"
],
[
"e",
"391c787c8745d1a52c1830e6bc04c275be8cadefa786388277ba4df121f05835",
"",
"reply"
],
[
"p",
"f2c95df3766562e3b96b79a0254881c59e8639f23987846961cf55412a77f6f2"
]
],
"content": "📅 Original date posted:2011-12-21\n🗒️ Summary of this message: Mike Hearn asks if there is a way to improve Git's summaries for merge commits. Suggestion given to use `git log --no-merges`.\n📝 Original message:On Wednesday, December 21, 2011 5:12:07 AM Mike Hearn wrote:\n\u003e Git does not produce very helpful summaries when every commit is a merge.\n\u003e Is there a way to fix that? You have to guess what a change does based on\n\u003e the name of the topic branch currently.\n\nNot sure what you mean. Maybe `git log --no-merges` ?",
"sig": "15e53a4a4cf8a0d140b55d1910e7035ee9bd8a2d05bec8b630735c175d80a8cf742924c8728d3667963dc4f09aa58a739c9756b12083b657877574f24a324c22"
}