From: "Gao, Liming" <liming.gao@intel.com>
To: Laszlo Ersek <lersek@redhat.com>,
"Shifflett, Joseph" <joseph.shifflett@hpe.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@ml01.01.org>
Subject: Re: Sourceforge svn mirror of edk2
Date: Thu, 9 Feb 2017 01:53:38 +0000 [thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14D6D8B69@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <46e5ebb4-41ef-2c55-d8dd-461fae4a4006@redhat.com>
Recently, our auto sync machine meets with some issue. We are working on it to let it work back asap.
Long term goal is to stop svn, and everyone uses edk2 git.
Thanks
Liming
-----Original Message-----
From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Laszlo Ersek
Sent: Wednesday, February 8, 2017 11:18 PM
To: Shifflett, Joseph <joseph.shifflett@hpe.com>
Cc: edk2-devel@lists.01.org <edk2-devel@ml01.01.org>
Subject: Re: [edk2] Sourceforge svn mirror of edk2
On 02/08/17 16:00, Shifflett, Joseph wrote:
> I apologize if this is not the best list.
It is the correct list, yes.
>
> There hasn't been a commit that was cherrypicked from the git repo
> into the sourceforge svn repo since 2/3.
>
> This was an automated process for the last year or two. Was it
> intentionally discontinued?
Yes, it was intentionally discontinued.
Official Wiki article about the git-based development workflow:
https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Development-Process
(See also further articles linked from therein.)
My personal recommendations (long article):
https://github.com/tianocore/tianocore.github.io/wiki/Laszlo's-unkempt-git-guide-for-edk2-contributors-and-maintainers
Thanks
Laszlo
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel
next prev parent reply other threads:[~2017-02-09 1:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-08 15:00 Sourceforge svn mirror of edk2 Shifflett, Joseph
2017-02-08 15:18 ` Laszlo Ersek
2017-02-08 16:56 ` Carsey, Jaben
2017-02-08 17:05 ` Laszlo Ersek
2017-02-09 1:53 ` Gao, Liming [this message]
2017-02-09 3:49 ` Gao, Liming
2017-02-09 9:14 ` Laszlo Ersek
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-list 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=4A89E2EF3DFEDB4C8BFDE51014F606A14D6D8B69@shsmsx102.ccr.corp.intel.com \
--to=devel@edk2.groups.io \
/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