From: Paulo Matos <pmatos@broadcom.com>
To: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: FW: Git repo lagging behing
Date: Tue, 04 Feb 2014 15:59:00 -0000 [thread overview]
Message-ID: <19EB96622A777C4AB91610E763265F4640669B@SJEXCHMB14.corp.ad.broadcom.com> (raw)
In-Reply-To: <19EB96622A777C4AB91610E763265F4640653C@SJEXCHMB14.corp.ad.broadcom.com>
Since the owner of the repo http://gcc.gnu.org/git/?p=gcc.git;a=summary is marked as being: gcc@gcc.gnu.org
moving this thread of the gcc mailing list.
Paulo Matos
-----Original Message-----
From: gcc-help-owner@gcc.gnu.org [mailto:gcc-help-owner@gcc.gnu.org] On Behalf Of Paulo Matos
Sent: 04 February 2014 14:08
To: gcc-help@gcc.gnu.org
Subject: Git repo lagging behing
Hi,
Don't know if anybody noticed but something's wrong with the git repo. It's lagging behind. Last commit there was:
18 hours ago tejohnson 2014-02-03 Teresa Johnson <tejohnson@google.com>
which was certainly not the last commit on trunk.
Paulo Matos
next parent reply other threads:[~2014-02-04 15:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <19EB96622A777C4AB91610E763265F4640653C@SJEXCHMB14.corp.ad.broadcom.com>
2014-02-04 15:59 ` Paulo Matos [this message]
2014-02-04 21:17 ` Marek Polacek
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=19EB96622A777C4AB91610E763265F4640669B@SJEXCHMB14.corp.ad.broadcom.com \
--to=pmatos@broadcom.com \
--cc=gcc@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).