Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Brian Murphy" <brian@murphy.dk>
To: "Ralf Baechle" <ralf@linux-mips.org>
Cc: <linux-mips@linux-mips.org>
Subject: Re: [PATCH] Add back support for LASAT platforms
Date: Tue, 28 Aug 2007 11:24:54 -0000	[thread overview]
Message-ID: <twig.1188300294.58543@mail.murphy.dk> (raw)
In-Reply-To: <20070823200844.GA31558@linux-mips.org>

On Thu, Aug 23, 2007, Ralf Baechle <ralf@linux-mips.org> said:

> On Thu, Aug 23, 2007 at 09:49:37PM +0200, Brian Murphy wrote:
> 
>> >So with plenty of fixes your code is now in the -queue tree and you may
>> >want to test if it's still in good working order and as usual there is
>> >always a little more that could be cleaned and polished ...
>> >
>> >  
>> Thanks. I couldn't find the code in the -queue tree but it seems to
>> be in the upstream tree, is this correct?
> 
> It was in the tree on my laptop only because I was working on the patch
> offline last night so couldn't upload it and forgot to do it later, sorry.
> The latest -queue tree is now online.
> 
>   Ralf
> 

-- 

I can git-clone the tree but am having some difficulty in seeing / cloning
the queue head where the changes are. What is the magic git incantation
that does this?

/Brian

WARNING: multiple messages have this Message-ID (diff)
From: "Brian Murphy" <brian@murphy.dk>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH] Add back support for LASAT platforms
Date: Tue, 28 Aug 2007 11:24:54 -0000	[thread overview]
Message-ID: <twig.1188300294.58543@mail.murphy.dk> (raw)
Message-ID: <20070828112454.a8VF55mgFfKFfpD6X0sd5z9Gb-oqKN15s5oFACYCWew@z> (raw)
In-Reply-To: <20070823200844.GA31558@linux-mips.org>

On Thu, Aug 23, 2007, Ralf Baechle <ralf@linux-mips.org> said:

> On Thu, Aug 23, 2007 at 09:49:37PM +0200, Brian Murphy wrote:
> 
>> >So with plenty of fixes your code is now in the -queue tree and you may
>> >want to test if it's still in good working order and as usual there is
>> >always a little more that could be cleaned and polished ...
>> >
>> >  
>> Thanks. I couldn't find the code in the -queue tree but it seems to
>> be in the upstream tree, is this correct?
> 
> It was in the tree on my laptop only because I was working on the patch
> offline last night so couldn't upload it and forgot to do it later, sorry.
> The latest -queue tree is now online.
> 
>   Ralf
> 

-- 

I can git-clone the tree but am having some difficulty in seeing / cloning
the queue head where the changes are. What is the magic git incantation
that does this?

/Brian

  reply	other threads:[~2007-08-28 11:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-21 20:34 [PATCH] Add back support for LASAT platforms brm
2007-08-22  1:14 ` Yoichi Yuasa
2007-08-22  6:59   ` Geert Uytterhoeven
2007-08-22 23:24     ` Ralf Baechle
2007-08-22 20:35   ` Brian Murphy
2007-08-23  1:17     ` Yoichi Yuasa
2007-08-23 12:32 ` Ralf Baechle
2007-08-23 19:49   ` Brian Murphy
2007-08-23 20:08     ` Ralf Baechle
2007-08-28 11:24       ` Brian Murphy [this message]
2007-08-28 11:24         ` Brian Murphy
2007-08-28 12:40         ` Ralf Baechle

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=twig.1188300294.58543@mail.murphy.dk \
    --to=brian@murphy.dk \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.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