On Wed, 2013-06-19 at 09:10 +0200, Francis Moreau wrote:
> Hi,
>
> On Tue, Jun 18, 2013 at 10:44 PM, Ben Hutchings <ben@xxxxxxxxxxxxxxx> wrote:
> > On Tue, Jun 18, 2013 at 12:16:14PM -0700, Greg KH wrote:
> >> On Tue, Jun 18, 2013 at 09:10:32PM +0200, Francis Moreau wrote:
> >> > Hi Greg,
> >>
> >> <Fixing the stable kernel mailing list address...>
> >>
> >> > On Tue, Jun 18, 2013 at 4:34 PM, Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> wrote:
> >> >
> >> > > On Tue, Jun 18, 2013 at 10:55:56AM +0200, Francis Moreau wrote:
> >> > > > Hi,
> >> > > >
> >> > > > I'd like to write a tool that would parse the message of commits in a
> >> > > stable
> >> > > > tree and retrieves the associated upstream commits.
> >> > > >
> >> > > > It seems that stable commits provides this information through their log:
> >> > > >
> >> > > > "commit xxxxxxxx upstream."
> >
> > Currently there are 3 different formats used for backports of a single
> > commit, which are:
> >
> > gregkh: commit $HASH upstream.
> > davem: [ Upstream commit $HASH ]
>
> ah thanks I missed the last one :)
>
> > git-cherry-pick: (cherry-picked from commit $HASH)
>
> is this format used by any stable trees ?
[...]
So far as I know, all currently-maintained stable branches have a
mixture of these.
Ben.
--
Ben Hutchings
Lowery's Law:
If it jams, force it. If it breaks, it needed replacing anyway.
Attachment:
signature.asc
Description: This is a digitally signed message part