public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tobias Burnus <tobias@codesourcery.com>
To: "Martin Liška" <mliska@suse.cz>,
	"Martin Sebor" <msebor@gmail.com>,
	"Jason Merrill" <jason@redhat.com>
Cc: Jakub Jelinek <jakub@redhat.com>,
	gcc Mailing List <gcc@gcc.gnu.org>,
	Jonathan Wakely <jwakely@redhat.com>,
	gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [RFC][PATCH] contrib: add git-commit-mklog wrapper
Date: Tue, 22 Jun 2021 10:23:55 +0200	[thread overview]
Message-ID: <54558c0c-e3e4-b369-1a4c-34a5517f7bae@codesourcery.com> (raw)
In-Reply-To: <ab959aa3-2763-7be6-409c-08bd6b0235e2@suse.cz>

Hello,

On 22.06.21 09:30, Martin Liška wrote:
> There's a patch candidate that comes up with a wrapper for 'git
> commit-mklog' alias.
> Using my patch, one can do:
> $ git commit-mklog -a -b 12345,
> Thoughts?

What about '-p' – to fetch the data from GCC Bugzilla? I do note that
'git commit ' supports '-p, --patch' which may or may not be an issue.

Tobias

-----------------
Mentor Graphics (Deutschland) GmbH, Arnulfstrasse 201, 80634 München Registergericht München HRB 106955, Geschäftsführer: Thomas Heurung, Frank Thürauf

  reply	other threads:[~2021-06-22  8:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <YMHe/JbcYEm0HZ35@redhat.com>
     [not found] ` <CACb0b4=YG4p2ESJ-2QaObqwi8=JLEMGu9oRAi4JrWOyumo+8ZA@mail.gmail.com>
     [not found]   ` <3228435b-aba0-6157-3266-c0f025822829@gmail.com>
     [not found]     ` <5f89ddc0-aed4-2c20-0979-dfafb29046ee@gmail.com>
     [not found]       ` <20210610173005.GI7746@tucnak>
     [not found]         ` <e7663f13-e07c-01ed-d4c3-1500d0e52c6e@gmail.com>
     [not found]           ` <20210610190941.GJ7746@tucnak>
     [not found]             ` <cae4bbbc-3104-f01d-83c8-19ae740c3500@gmail.com>
     [not found]               ` <CACb0b4kOavxRNMETn=UZx+kOabZ9wqaz7QpOLXpJ+LYdxvZWzw@mail.gmail.com>
     [not found]                 ` <58b63929-01f5-038c-931c-9ff8349d9f95@gmail.com>
     [not found]                   ` <CACb0b4nNAyhqJaap2N6XveABTUxKRew=knMDr6qZM1CZGOTwfw@mail.gmail.com>
     [not found]                     ` <fdee1b46-c44b-eb57-abd7-1ef3b4d2b756@gmail.com>
     [not found]                       ` <alpine.BSF.2.20.16.2106152045070.98326@arjuna.pair.com>
     [not found]                         ` <cf56da64-451b-d33f-278d-cbbfee28aaa7@gmail.com>
     [not found]                           ` <CADzB+2mO0hpCyeON0-6fM=ngTJSdxSceedyL+zbEDYmAyTUL9Q@mail.gmail.com>
     [not found]                             ` <c02221d2-8b74-bc19-4bed-68103efa31d0@redhat.com>
     [not found]                               ` <d1b914d8-ce31-5540-2d7f-76152b7b8444@gmail.com>
     [not found]                                 ` <CADzB+2kCLfEcpYmco6QLyU69hTxw7zD=x5LZ09Ki+1qr6Oss_A@mail.gmail.com>
     [not found]                                   ` <71b4a023-efb2-6c6a-9ced-93cce7c96540@gmail.com>
2021-06-21  7:54                                     ` [Patch, v2] contrib/mklog.py: Improve PR handling (was: Re: git gcc-commit-mklog doesn't extract PR number to ChangeLog) Tobias Burnus
2021-06-21  8:09                                       ` Martin Liška
2021-06-21  8:37                                         ` Tobias Burnus
2021-06-21 12:53                                           ` Martin Liška
2021-06-21 13:26                                             ` Tobias Burnus
2021-06-22  7:30                                               ` [RFC][PATCH] contrib: add git-commit-mklog wrapper Martin Liška
2021-06-22  8:23                                                 ` Tobias Burnus [this message]
2021-06-22  8:31                                                   ` Martin Liška
2021-06-22 18:40                                                 ` Jason Merrill
2021-06-23  7:40                                                   ` Martin Liška

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=54558c0c-e3e4-b369-1a4c-34a5517f7bae@codesourcery.com \
    --to=tobias@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=jason@redhat.com \
    --cc=jwakely@redhat.com \
    --cc=mliska@suse.cz \
    --cc=msebor@gmail.com \
    /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).