All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Abbott <abbotti@mev.co.uk>
To: Spencer Olson <olsonse@umich.edu>
Cc: devel@driverdev.osuosl.org,
	H Hartley Sweeten <hsweeten@visionengravers.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	stable@vger.kernel.org
Subject: Re: [PATCH v2] staging: comedi: ni_tiocmd: change mistaken use of start_src for start_arg
Date: Wed, 13 Jan 2016 10:36:11 +0000	[thread overview]
Message-ID: <5696289B.3020806@mev.co.uk> (raw)
In-Reply-To: <CAOx9PeiUWp6DPw+PFKDyZXc1s3kF9pGfhW1oc+JSZ3nGf-5_Mw@mail.gmail.com>

On 12/01/16 18:01, Spencer Olson wrote:
> I looked through commit messages in the repository that also had Fixes:
> tags that were long.  The ones I looked at were all split.  I was going
> to say everything, but I just noticed that I was looking at some commits
> from 2014.  I don't mind resubmitting if current tools require that or
> it is better for some other reason...

Yes, you're correct.  This command shows quite a few that are presumably 
split over more than one line:

git log | grep '^ *Fixes: [0-9a-f]* (.*[^)]$' | more

-- 
-=( Ian Abbott @ MEV Ltd.    E-mail: <abbotti@mev.co.uk> )=-
-=(                          Web: http://www.mev.co.uk/  )=-

  parent reply	other threads:[~2016-01-13 10:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <56951A9A.8060409@mev.co.uk>
2016-01-12 17:33 ` [PATCH v2] staging: comedi: ni_tiocmd: change mistaken use of start_src for start_arg Spencer E. Olson
2016-01-12 17:56   ` Ian Abbott
     [not found]     ` <CAOx9PeiUWp6DPw+PFKDyZXc1s3kF9pGfhW1oc+JSZ3nGf-5_Mw@mail.gmail.com>
2016-01-13 10:36       ` Ian Abbott [this message]
2016-01-13 10:56         ` Dan Carpenter
2016-01-12 22:12   ` Dan Carpenter
2016-01-13 10:37   ` Ian Abbott

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=5696289B.3020806@mev.co.uk \
    --to=abbotti@mev.co.uk \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hsweeten@visionengravers.com \
    --cc=olsonse@umich.edu \
    --cc=stable@vger.kernel.org \
    /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.