Message ID | pull.1602.git.git.1698610987926.gitgitgadget@gmail.com (mailing list archive) |
---|---|
State | Accepted |
Commit | 8f81532599aa59900266f231d107944eef0453d9 |
Headers | show |
Series | chore: fix typo in .clang-format comment | expand |
On Sun, Oct 29, 2023 at 08:23:07PM +0000, Aditya Neelamraju via GitGitGadget wrote:
> From: Aditya Neelamraju <adityanv97@gmail.com>
We typically prefix commit messages with the subject area they're
working in, not with "chore", or "feat" like some Git workflows
recommend.
That said, the contents of this patch look obviously correct to me.
Thanks for noticing and fixing!
Thanks,
Taylor
Taylor Blau <me@ttaylorr.com> writes: > On Sun, Oct 29, 2023 at 08:23:07PM +0000, Aditya Neelamraju via GitGitGadget wrote: >> From: Aditya Neelamraju <adityanv97@gmail.com> > > We typically prefix commit messages with the subject area they're > working in, not with "chore", or "feat" like some Git workflows > recommend. > ... > That said, the contents of this patch look obviously correct to me. > Thanks for noticing and fixing! As a comment for a new contributor, it is a bit unhelpful not to suggest what the "subject area" string we would use if we were working on this patch, I think. I also suspected that valuve may be a valid word in some language, as the indentation in the example looked as if the six-letter word was meant, not typoed. https://www.gasolineravaluve.com/ was one of the first hits I saw in my search ;-)
On Tue, Oct 31, 2023 at 12:12:43PM +0900, Junio C Hamano wrote: > Taylor Blau <me@ttaylorr.com> writes: > > > On Sun, Oct 29, 2023 at 08:23:07PM +0000, Aditya Neelamraju via GitGitGadget wrote: > >> From: Aditya Neelamraju <adityanv97@gmail.com> > > > > We typically prefix commit messages with the subject area they're > > working in, not with "chore", or "feat" like some Git workflows > > recommend. > > ... > > That said, the contents of this patch look obviously correct to me. > > Thanks for noticing and fixing! > > As a comment for a new contributor, it is a bit unhelpful not to > suggest what the "subject area" string we would use if we were > working on this patch, I think. Good suggestion. I would have suggested "clang-format", which is exactly Aditya ended up choosing, anyway. Thanks, Aditya! > I also suspected that valuve may be a valid word in some language, > as the indentation in the example looked as if the six-letter word > was meant, not typoed. https://www.gasolineravaluve.com/ was one > of the first hits I saw in my search ;-) ;-) Thanks, Taylor
Taylor Blau <me@ttaylorr.com> writes: >> As a comment for a new contributor, it is a bit unhelpful not to >> suggest what the "subject area" string we would use if we were >> working on this patch, I think. > > Good suggestion. I would have suggested "clang-format", which is > exactly Aditya ended up choosing, anyway. Thanks, Aditya! Thanks. I was being lazy when I said the above ;-) Teaching how to fish instead of giving fish, the way I would have done is $ git log --no-merges --stat --full-diff .clang-format and inspect what they use. The ones that used "clang-format:" are indeed very similar in spirit to what this one does, I would say. Thanks.
diff --git a/.clang-format b/.clang-format index c592dda681f..3ed4fac753a 100644 --- a/.clang-format +++ b/.clang-format @@ -83,9 +83,9 @@ BinPackParameters: true BreakBeforeBraces: Linux # Break after operators -# int valuve = aaaaaaaaaaaaa + -# bbbbbb - -# ccccccccccc; +# int value = aaaaaaaaaaaaa + +# bbbbbb - +# ccccccccccc; BreakBeforeBinaryOperators: None BreakBeforeTernaryOperators: false