From: Jon Turney <jon.turney@dronecode.org.uk>
To: Johannes Schindelin <johannes.schindelin@gmx.de>,
Cygwin Patches <cygwin-patches@cygwin.com>
Subject: Re: [PATCH] Cygwin: Improve FAQ on early breakpoint for ASLR
Date: Wed, 14 Dec 2022 17:37:35 +0000 [thread overview]
Message-ID: <5de5fda5-b43c-affd-2c61-ad9986c1bf96@dronecode.org.uk> (raw)
In-Reply-To: <769CE863-866A-4E6B-A7D6-8EFA09B5D9F8@gmx.de>
On 11/12/2022 14:45, Johannes Schindelin wrote:
> On December 11, 2022 2:54:02 PM GMT+01:00, Jon Turney <jon.turney@dronecode.org.uk> wrote:
>> On 05/12/2022 15:23, Johannes Schindelin wrote:
>>> On Mon, 28 Nov 2022, Corinna Vinschen wrote:
>>>> On Nov 28 13:00, Jon Turney wrote:
>>>>> On 15/11/2022 10:46, Corinna Vinschen wrote:
>>>>>>
>>>>>> It would be great if we could get used to using the same syntax as the
>>>>>> Linux kernel project to document stuff. I'm trying to follow their lead
>>>>>> for a while. For fixes to former commits, it looks like this in the
>>>>>> kernel, at the end of the commit message:
>>>>>>
>>>>>> Fixes: 123456789012 ("title of commit 123456789012")
>>>>>>
>>>>>> Yeah, core.abbrev is 12 digits. I'm using this setting for quite some
>>>>>> time locally.
>>>>>
>>>>> Sounds good. Is there some script to automate generating this kind of
>>>>> comment from a commit-id?
>>>>
>>>> I don't think so, at least I don't see anything like that in git docs...
>>>
>>> It's note _quite_ what you asked for, but `git show --pretty=reference -s
>>> <commit>` (https://git-scm.com/docs/git-show#_pretty_formats) gives you
>>> _almost_ what you are looking for.
>>>
>>> But you can always call `git show -s --format='%h ("%s")' <commit>`, and
>>> even configure an alias for this:
>>>
>>> git config --global alias.pretty-print-commit \
>>> "-c core.abbrev=12 show -s --format='%h (\"%s\")'"
>>>
>> Thanks!
>>
>> I added '-c core.pager=', but this is what I was looking for, to save a
>> bit of copying and pasting and editing.
>>
>
> Better use `git -P`, then... (see https://git-scm.com/docs/git#Documentation/git.txt--P for full details)
>
I started off with that, but that fails when used with:
fatal: alias 'pretty-print-commit' changes environment variables.
You can use '!git' in the alias to do this
... which I'm sure tells me the right way to write this :)
next prev parent reply other threads:[~2022-12-14 17:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 17:04 Jon Turney
2022-11-03 18:22 ` Jeremy Drake
2022-11-04 10:34 ` Corinna Vinschen
2022-11-04 12:53 ` Jon Turney
2022-11-04 13:16 ` Corinna Vinschen
2022-11-04 15:29 ` Pedro Alves
2022-11-12 14:30 ` Jon Turney
2022-11-15 10:46 ` Corinna Vinschen
2022-11-28 13:00 ` Jon Turney
2022-11-28 14:41 ` Corinna Vinschen
2022-12-05 15:23 ` Johannes Schindelin
2022-12-11 13:54 ` Jon Turney
2022-12-11 14:45 ` Johannes Schindelin
2022-12-14 17:37 ` Jon Turney [this message]
2023-03-28 8:26 ` Johannes Schindelin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5de5fda5-b43c-affd-2c61-ad9986c1bf96@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-patches@cygwin.com \
--cc=johannes.schindelin@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).