From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Hans de Goede <hdegoede@redhat•com>
Cc: Mark Gross <mark.gross@intel•com>,
Vadim Pasternak <vadimp@nvidia•com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the drivers-x86 tree
Date: Mon, 30 Nov 2020 18:58:51 +1100 [thread overview]
Message-ID: <20201130185851.0884bd9f@canb.auug.org.au> (raw)
In-Reply-To: <ae231b40-e1c8-6995-d45b-ddab6a04810e@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 663 bytes --]
Hi Hans,
On Mon, 30 Nov 2020 08:43:21 +0100 Hans de Goede <hdegoede@redhat•com> wrote:
>
> Question, how important is it to fix these ? I normally never do forced pushes
> to the for-next branch. But if this is considered important to fix I guess I
> can make an exception.
I think it is fine to leave these, but to try to not have more in the future.
> Will git rewrite the commit msg when this is set ? I'm at 2.28 and don't
> have core.abbrev set. But I guess this needs to be set in the gitconfig
> of the creator of the patch; and this has no impact on "git am" ?
It will not rewrite the commit message.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-11-30 7:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-29 17:43 linux-next: Fixes tag needs some work in the drivers-x86 tree Stephen Rothwell
2020-11-30 7:43 ` Hans de Goede
2020-11-30 7:58 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-18 21:06 Stephen Rothwell
2024-11-20 14:02 ` Hans de Goede
2022-03-01 21:17 Stephen Rothwell
2022-03-02 11:17 ` Hans de Goede
2021-11-01 21:37 Stephen Rothwell
2021-11-02 10:28 ` Hans de Goede
2021-08-10 22:16 Stephen Rothwell
2021-08-12 7:40 ` Hans de Goede
2021-03-08 6:06 Stephen Rothwell
2021-03-08 10:36 ` Hans de Goede
2020-04-23 22:53 Stephen Rothwell
2020-04-24 9:46 ` Andy Shevchenko
2019-06-11 21:43 Stephen Rothwell
2019-04-16 21:33 Stephen Rothwell
2019-02-06 22:57 Stephen Rothwell
[not found] ` <38152c55-c2c1-c89f-2751-0ef0d40fcba9@linux.intel.com>
2019-02-07 15:55 ` Andy Shevchenko
2019-02-13 15:15 ` Bhardwaj, Rajneesh
2019-02-21 0:40 ` Darren Hart
2019-02-21 13:36 ` Andy Shevchenko
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=20201130185851.0884bd9f@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=hdegoede@redhat$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mark.gross@intel$(echo .)com \
--cc=vadimp@nvidia$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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