public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Hutchings <ben@decadent.org.uk>
To: dmg <dmg@uvic.ca>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: helping with tracking commits across repos
Date: Mon, 15 Apr 2013 19:39:09 +0100	[thread overview]
Message-ID: <20130415183909.GQ2619@decadent.org.uk> (raw)
In-Reply-To: <CAEBXXD8CZumwvOH7gLU+HQNAngHbD7eLFB48qUF_8BeYhk7fNQ@mail.gmail.com>

On Mon, Apr 15, 2013 at 11:21:32AM -0700, dmg wrote:
> Hi Ben,
> 
> On 4/13/13, Ben Hutchings <ben@decadent.org.uk> wrote:
[...]
> > It should be possible to find such backported commits based on a simple
> > regex search over the commit message:
> 
> I took a more aggressive approach. I decided to look for 40 length
> character hashes in the
> comment and patch of the commit.
[...]
> hopefully this solves the use-case you described.

That's great, thankyou.

> The commit logs are being scanned as I write this. It should be done
> in a couple of hours.
 
By the way, I noticed that you're not HTML-escaping the commit
header.

Ben.

-- 
Ben Hutchings
We get into the habit of living before acquiring the habit of thinking.
                                                              - Albert Camus

      reply	other threads:[~2013-04-15 18:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-12 20:22 helping with tracking commits across repos D M German
2013-04-12 20:31 ` Greg KH
2013-04-13 18:01   ` D M German
2013-04-13 18:56     ` D M German
2013-04-16 12:50     ` Luis Henriques
2013-04-15 21:49   ` D M German
2013-04-15 23:09     ` Greg KH
2013-04-16  0:13       ` D M German
2013-04-16  4:40         ` Greg KH
2013-04-24  6:26           ` D M German
2013-04-13 16:18 ` Vinod Koul
2013-04-14  4:01 ` Ben Hutchings
2013-04-15 18:21   ` dmg
2013-04-15 18:39     ` Ben Hutchings [this message]

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=20130415183909.GQ2619@decadent.org.uk \
    --to=ben@decadent.org.uk \
    --cc=dmg@uvic.ca \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox