On Tue, Oct 6, 2020 at 8:43 AM Don Zickus <dzickus(a)redhat.com>
wrote:
> On Tue, Oct 06, 2020 at 07:12:44AM -0500, Justin Forbes wrote:
>>> Would be nice if those could be links to the commits in question,
>>> as that makes it easy to look at them. How about something like this:
>>> $ git log --no-merges --pretty=oneline --no-decorate master..$EXCLUDE_FILES |
sed 's!^!https://gitlab.com/cki-project/kernel-ark/-/commit/!; s! !\n !; s!$!\n!'
> $SOURCES/Patchlist.changelog
>>> Then something (note: I did it with some random git tree I had at hand,
>>> not with kernel-ark, hence the URLs won't work) like this
>>>
>>> a755240762dd07bb48cf3e561b1e6cfa894f9178 docs: reporting-bugs: add SPDX tag
and license hint, remove markers
>>> 42d0e4956abf7ea2b0ea15f56afb1720a11739f1 docs: reporting-bugs: explain things
could be easier
>>> aac1d02c1ca7d4a20dfe47ae6f824e1091c654e3 docs: reporting-bugs: explain why
users might get neither reply nor fix
>>>
>>>
>>> Becomes
>>>
https://gitlab.com/cki-project/kernel-ark/-/commit/a755240762dd07bb48cf3e...
>>> docs: reporting-bugs: add SPDX tag and license hint, remove markers
>>>
>>>
https://gitlab.com/cki-project/kernel-ark/-/commit/42d0e4956abf7ea2b0ea15...
>>> docs: reporting-bugs: explain things could be easier
>>>
>>>
https://gitlab.com/cki-project/kernel-ark/-/commit/aac1d02c1ca7d4a20dfe47...
>>> docs: reporting-bugs: explain why users might get neither reply nor fix
>>
>> This is not a bad update. I would be okay with this, though it does
>> make it less simple for people working in an actual git tree, having
>> to select the commit hash carefully vs just a double click to copy.
>
> I am in favor of this suggestion. We can retain the old output and just add
> a new line as suggested, that can satisfy both needs??
That would work well.