public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: "Martin Liška" <mliska@suse.cz>
Cc: Jakub Jelinek <jakub@redhat.com>,
	GCC Patches <gcc-patches@gcc.gnu.org>,
	binutils@sourceware.org, "H.J. Lu" <hjl.tools@gmail.com>
Subject: Re: [PATCH] PR lto/94249: Correct endianness detection with the __BYTE_ORDER macro
Date: Wed, 1 Apr 2020 18:28:46 +0100 (BST)	[thread overview]
Message-ID: <alpine.LFD.2.21.2004011821160.4156324@eddie.linux-mips.org> (raw)
In-Reply-To: <61fdce93-0da7-3bda-6a78-c5a072304d6d@suse.cz>

On Wed, 1 Apr 2020, Martin Liška wrote:

> > commit 142d68f50b48309f48e34fc1d9d6dbbeecfde684
> > Author:     Martin Liska <mliska@suse.cz>
> > AuthorDate: Wed Apr 1 09:37:37 2020 +0200
> > Commit:     Martin Liska <mliska@suse.cz>
> > CommitDate: Wed Apr 1 09:37:37 2020 +0200
> > 
> > You're still listed as the author of the change in question.
> 
> It's the first time anybody is asking me for that. I considered the ChangeLog
> entry as sufficient. Anyway, next time please send a patch with git
> format-patch
> so that one can apply it with git am. That will preserve you as the author.

 Of course it was formatted for `git am', I've been doing that for many 
years now for all the pieces of the toolchain (even with GCC while it was 
still on SVN).  Had you fed the message to `git am', it would have done 
the right thing.

> Or ideally, feel free to fulfil copyright assignment and install commits
> by your own.

 I've had it for some 20 years now for GCC and other pieces of the GNU
toolchain.  Otherwise I couldn't have been listed in MAINTAINERS.

 Why did you come up with an idea that I haven't?

  Maciej

  reply	other threads:[~2020-04-01 17:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200323103505.GF2156@tucnak>
     [not found] ` <6313e487-6dbb-ac17-4160-4ac600af40be@suse.cz>
     [not found]   ` <7369b1aa-be0d-92cc-4f81-1612f101e2e8@suse.cz>
     [not found]     ` <CAFiYyc3yKQpWzh3Yzh7b40adi=gtFmYLeEZex_yCqYGSOdFcEw@mail.gmail.com>
     [not found]       ` <CAMe9rOqQf+3wO2rosK-jCNYEqc3e-OMP3NtVH0EX26aKGaFeBg@mail.gmail.com>
     [not found]         ` <3786da05-1530-38c5-e9e2-cd69418cd42a@suse.cz>
     [not found]           ` <CAMe9rOpFyGpzQwqsmz0ikZz3MhY4FsZYv_+jCNAHq0768vPw5Q@mail.gmail.com>
     [not found]             ` <5b27738a-9885-9906-0c93-888daf4a066f@suse.cz>
     [not found]               ` <20200324083109.GP2156@tucnak>
     [not found]                 ` <e96704f3-9025-48af-f894-81401a5718a4@suse.cz>
     [not found]                   ` <20200324091805.GQ2156@tucnak>
     [not found]                     ` <b5a25c37-d29c-b636-04ef-eba959ad495b@suse.cz>
2020-03-31 13:27                       ` Maciej W. Rozycki
2020-04-01  5:01                         ` Hans-Peter Nilsson
2020-04-01  7:43                           ` Martin Liška
2020-04-01 23:57                             ` Hans-Peter Nilsson
2020-04-01  7:17                         ` Richard Biener
2020-04-01  7:41                         ` Martin Liška
2020-04-01  9:55                           ` Maciej W. Rozycki
2020-04-01 10:01                             ` Martin Liška
2020-04-01 15:59                               ` Maciej W. Rozycki
2020-04-01 16:54                                 ` Martin Liška
2020-04-01 17:28                                   ` Maciej W. Rozycki [this message]
2020-04-01 10:04                           ` Maciej W. Rozycki
2020-04-01 10:09                             ` 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=alpine.LFD.2.21.2004011821160.4156324@eddie.linux-mips.org \
    --to=macro@linux-mips.org \
    --cc=binutils@sourceware.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hjl.tools@gmail.com \
    --cc=jakub@redhat.com \
    --cc=mliska@suse.cz \
    /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).