From: Joe Perches <joe@perches.com>
To: Jason Gunthorpe <jgg@mellanox.com>
Cc: Matteo Croce <mcroce@redhat.com>,
Doug Ledford <dledford@redhat.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Potnuri Bharat Teja <bharat@chelsio.com>
Subject: Re: linux-next: Fixes tag needs some work in the rdma-fixes tree
Date: Mon, 21 Oct 2019 12:32:47 -0700 [thread overview]
Message-ID: <16d819ded0c1edb46af8914a26cad479aac176e9.camel@perches.com> (raw)
In-Reply-To: <20191021173921.GD6285@mellanox.com>
On Mon, 2019-10-21 at 17:39 +0000, Jason Gunthorpe wrote:
> Maybe output format and then parse it to check the min
> length and verify the subject?
I'm not too worried about that for now.
12 should still be good for quite awhile...
$ git log --abbrev=1 --format='%h' --no-merges | \
awk '{print length($1);}' | sort -n | uniq -c
90 5
463746 6
320183 7
26244 8
1683 9
118 10
6 11
next prev parent reply other threads:[~2019-10-21 19:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-21 7:41 linux-next: Fixes tag needs some work in the rdma-fixes tree Stephen Rothwell
2019-10-21 14:50 ` Doug Ledford
2019-10-21 15:15 ` Jason Gunthorpe
2019-10-21 15:39 ` Matteo Croce
2019-10-21 17:01 ` Jason Gunthorpe
2019-10-21 17:08 ` Matteo Croce
2019-10-21 17:11 ` Jason Gunthorpe
2019-10-21 17:25 ` Joe Perches
2019-10-21 17:39 ` Jason Gunthorpe
2019-10-21 19:32 ` Joe Perches [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-05 22:03 Stephen Rothwell
2024-02-06 15:17 ` Jason Gunthorpe
2022-09-08 10:11 Stephen Rothwell
2019-04-22 20:57 Stephen Rothwell
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=16d819ded0c1edb46af8914a26cad479aac176e9.camel@perches.com \
--to=joe@perches.com \
--cc=bharat@chelsio.com \
--cc=dledford@redhat.com \
--cc=jgg@mellanox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mcroce@redhat.com \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.