From: "Chautru, Nicolas" <nicolas.chautru@intel.com>
To: David Christensen <drc@linux.vnet.ibm.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Anyone Having Issues with Git Repository Access?
Date: Mon, 15 Jul 2019 18:54:07 +0000 [thread overview]
Message-ID: <1183128033837D43A851F70F33ED5C575C1F9A3B@FMSMSX109.amr.corp.intel.com> (raw)
In-Reply-To: <842f1acf-ff52-ffeb-49df-98ea45499262@linux.vnet.ibm.com>
Hi David,
I believe that this is just confusion because of the way git tracks commit date. Even if last commit is" June-24", this is the date of when the commit was created, not when it was merged. You can see July dates in history.
This looks fine to me basically and latest is on master.
Cheers
Nic
-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of David Christensen
Sent: Monday, July 15, 2019 11:24 AM
To: dev@dpdk.org
Subject: [dpdk-dev] Anyone Having Issues with Git Repository Access?
When I clone the repositories at http://dpdk/org/git/dpdk or git://dpdk.org/dpdk I'm only seeing commits up through June 24 in the log, but the web interface to the development repo at https://git.dpdk.org/dpdk/ shows commits through today. I see the same behavior on when accessed from the office and from home, so it seems like an issue at the upstream repository.
Dave
prev parent reply other threads:[~2019-07-15 18:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-15 18:24 David Christensen
2019-07-15 18:54 ` Chautru, Nicolas [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=1183128033837D43A851F70F33ED5C575C1F9A3B@FMSMSX109.amr.corp.intel.com \
--to=nicolas.chautru@intel.com \
--cc=dev@dpdk.org \
--cc=drc@linux.vnet.ibm.com \
/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 NNTP newsgroup(s).