From: Greg Ungerer <gerg@snapgear.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux/m68k <linux-m68k@vger.kernel.org>,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
uClinux development list <uclinux-dev@uclinux.org>,
Greg Ungerer <gerg@uclinux.org>
Subject: Re: merge of m68knommu and m68k arch branches?
Date: Fri, 18 Mar 2011 09:59:36 +1000 [thread overview]
Message-ID: <4D82A068.7020101@snapgear.com> (raw)
In-Reply-To: <AANLkTimtr0JbmM2PNtGRyAKE7kNr_FXd==ZC3bM82xsG@mail.gmail.com>
Hi Geert,
Looks like we both have our changes for m68k and m68knommu in Linus'
git tree for this merge window. Do you plan to push anything else?
If you are done I will prepare a single git commit on the m68knommu
git tree that merges the m68knommu and m68k arch branches. I will
post here again for one last check over early next week, and if
everyone is happy I will ask Linus to pull it later next week.
How does that sound?
Regards
Greg
------------------------------------------------------------------------
Greg Ungerer -- Principal Engineer EMAIL: gerg@snapgear.com
SnapGear Group, McAfee PHONE: +61 7 3435 2888
8 Gardner Close FAX: +61 7 3217 5323
Milton, QLD, 4064, Australia WEB: http://www.SnapGear.com
next prev parent reply other threads:[~2011-03-18 0:01 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-18 0:07 merge of m68knommu and m68k arch branches? Greg Ungerer
2011-02-18 7:44 ` Sam Ravnborg
2011-02-18 7:44 ` Sam Ravnborg
2011-02-18 12:01 ` Greg Ungerer
2011-02-21 21:43 ` Arnd Bergmann
2011-02-21 21:57 ` Sam Ravnborg
2011-02-18 11:27 ` Geert Uytterhoeven
2011-02-18 15:24 ` Geert Uytterhoeven
2011-02-18 15:24 ` Geert Uytterhoeven
2011-02-18 22:12 ` Greg Ungerer
2011-02-19 8:39 ` Geert Uytterhoeven
2011-02-20 23:53 ` Greg Ungerer
2011-02-20 23:53 ` Greg Ungerer
2011-02-21 7:41 ` Geert Uytterhoeven
2011-03-17 23:59 ` Greg Ungerer [this message]
2011-03-18 7:24 ` Geert Uytterhoeven
2011-03-18 7:24 ` Geert Uytterhoeven
2011-02-21 21:18 ` Thomas Gleixner
2011-02-22 2:05 ` Greg Ungerer
2011-02-22 7:14 ` Geert Uytterhoeven
2011-02-22 7:29 ` Sam Ravnborg
2011-02-22 7:29 ` Sam Ravnborg
2011-02-22 7:40 ` Geert Uytterhoeven
2011-02-22 8:04 ` Sam Ravnborg
2011-02-22 9:16 ` Thomas Gleixner
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=4D82A068.7020101@snapgear.com \
--to=gerg@snapgear.com \
--cc=geert@linux-m68k.org \
--cc=gerg@uclinux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=uclinux-dev@uclinux.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.