Displaying 20 results from an estimated 40000 matches similar to: "[LLVMdev] Subversion Conversion Delay"
2009 Mar 09
2
[LLVMdev] Power Outage at University of Illinois
Dear LLVMers,
There was a campus wide power outage today at the University of
Illinois. It took down most (if not all) computing services, including
the LLVM web/subversion server and the mailing list server.
Power has since been restored, and it appears that our IT department has
gotten the LLVM web and SVN server operating again (I went in earlier
this evening to see if the LLVM server
2007 Jun 25
0
[LLVMdev] Subversion Migration Delayed Again
Dear LLVMers,
The configuration of the subversion software is still incomplete, so we
will not be starting the switch over to SVN at 1:00 pm CDT today as planned.
I do not know yet when the conversion can be rescheduled. It looks like
tomorrow (Tuesday) is the earliest that we can begin the conversion.
I'll keep the list updated as I learn more details.
-- John T.
2007 Jun 29
6
[LLVMdev] Subversion Migration Completed
Dear LLVMers,
The first phase of the Subversion conversion is complete. The CVS
repository will no longer be available. You will now need to use the
SVN server.
Directions for getting LLVM from the SVN server can be found in the new
Getting Started Guide (http://llvm.org/docs/GettingStarted.html). If
you run a nightly tester, you should update your LLVM tree from SVN to
get the new
2009 Nov 14
1
[LLVMdev] SAFECode Source Code Released
Török Edwin wrote:
> On 2009-11-14 00:57, John Criswell wrote:
>
>> Dear LLVMers,
>>
>> We are happy to announce an alpha release of the SAFECode compiler. It
>> is now available for download from the LLVM public Subversion
>> repository. SAFECode uses a set of analysis passes and program
>> transformations to provide strong memory safety
2007 Jun 15
0
[LLVMdev] migration to SubVersion successful or delayed?
Basile STARYNKEVITCH wrote:
> Dear All,
>
> according to http://llvm.org/SVNMigration.html the repository migrated to SubVersion (svn)
> on june 5th 2007 (almost 10 days ago).
>
The migration was delayed. The subversion software was supposed to be
configured this week by our IT department, but I have not heard from
them yet. I've fired off an email to see what the status
2007 Apr 21
0
[LLVMdev] Subversion Conversion: June 5th, 2007
All LLVM Developers:
This is your notice that the LLVM project is converting from CVS to
Subversion for its software repository. The conversion will happen on
June 5th, 2007 unless otherwise notified. Please see
http://llvm.org/SVNMigration.html for full details.
We had hoped to have the conversion done by now, but a number of factors
made it prudent for us to delay for a few more weeks. There
2007 Jun 26
0
[LLVMdev] Subversion Conversion (IMPORTANT)
On Tue, 26 Jun 2007, Reid Spencer wrote:
> I know we've cried wolf before, but the conversion of the LLVM projects'
> software to use Subversion instead of CVS *WILL* occur on Friday June
> 29th with the following approximate schedule:
Great, I'm glad to see this happening. Thanks for making it happen.
One request: when the change goes live, please make sure the various
2009 Mar 09
1
[LLVMdev] Power Outage at University of Illinois
On Mar 8, 2009, at 10:55 PM, John Criswell wrote:
> Dear LLVMers,
>
> There was a campus wide power outage today at the University of
> Illinois. It took down most (if not all) computing services,
> including
> the LLVM web/subversion server and the mailing list server.
>
> Power has since been restored, and it appears that our IT department
> has
> gotten the
2007 Jun 26
2
[LLVMdev] Subversion Conversion (IMPORTANT)
All,
I know we've cried wolf before, but the conversion of the LLVM projects'
software to use Subversion instead of CVS *WILL* occur on Friday June
29th with the following approximate schedule:
* 09:00 CDT (14:00 UTC, 07:00 PDT) - CVS becomes read-only
(commits prevented)
* 09:05 CDT (14:05 UTC, 07:05 PDT) - Final conversion to SVN
starts
* 11:45 CDT
2007 Jun 29
0
[LLVMdev] Subversion Conversion Beginning
Dear All,
The Subversion Migration is beginning now. CVS commit access will be
disabled.
-- John T.
2010 Sep 14
0
[LLVMdev] LLVM SVN Repository Offline for Maintenance Tomorrow
Dear All,
Just a reminder that the maintenance will be commencing now.
-- John T.
John Criswell wrote:
> Dear LLVMers and Clangers,
>
> We'll be doing some maintenance on the LLVM repository on Tuesday, Sept.
> 14 (tomorrow). There were some files committed to the repository that
> we believe need to be removed from both mainline, the branches, and the
> revision
2007 Jun 15
3
[LLVMdev] migration to SubVersion successful or delayed?
Dear All,
according to http://llvm.org/SVNMigration.html the repository migrated to SubVersion (svn)
on june 5th 2007 (almost 10 days ago).
Did the migration happened as expected?
http://llvm.org/releases/ still mention CVS, and nothing on http://llvm.org/docs/GettingStarted.html#checkout suggest to
switch to svn instead of cvs.
What is the current best way to download the latest snapshot:
2008 Jul 08
1
[LLVMdev] Emergency Reboot of llvm.org
Dear LLVMers,
I will be rebooting the LLVM server in 5 minutes (3:35 pm Central
Time). The system is experiencing unusually high load, no other
remedies have lowered the load, and we think a reboot will fix it.
Please make sure any commits to the LLVM repository are done within the
next 5 minutes.
Thanks, and sorry for the inconvenience.
-- John T.
2010 Sep 14
6
[LLVMdev] LLVM SVN Repository Offline for Maintenance Tomorrow
Dear LLVMers and Clangers,
We'll be doing some maintenance on the LLVM repository on Tuesday, Sept.
14 (tomorrow). There were some files committed to the repository that
we believe need to be removed from both mainline, the branches, and the
revision history.
The SVN repository will go *off-line* at 7:00 am Central Daylight
Savings time on Tuesday. Please do not make any commits after
2007 Mar 03
0
[LLVMdev] Subversion Migration
On Fri, 2007-03-02 at 17:48 -0600, John Criswell wrote:
> Dear All,
>
> I've just heard that there's been a recent discussion on the IRC channel
> about moving the LLVM source repository from CVS to Subversion (SVN) and
> that this migration may happen "soon."
Yes, its been talked about for ages and its time to do it. We've debated
the choice of repositories
2007 Mar 02
4
[LLVMdev] Subversion Migration
Dear All,
I've just heard that there's been a recent discussion on the IRC channel
about moving the LLVM source repository from CVS to Subversion (SVN) and
that this migration may happen "soon."
Is such a migration being planned, and if so, what is the timeframe?
How will the migration be performed? I and other LLVM users have
deadlines in the near future, so we would like to
2007 Jun 29
3
[LLVMdev] Web Server back up
Dear All,
The LLVM web server is up and running, but we're still working on some
subversion configuration issues. The server may go up and down
intermittently as we try configuration changes over the next half hour.
Sorry for the inconvenience.
-- John T.
2010 Sep 14
1
[LLVMdev] LLVM SVN Repository Offline for Maintenance Tomorrow
John Criswell wrote:
> Dear All,
>
> Just a reminder that the maintenance will be commencing now.
>
Also, I managed to set things up so that you can use svn diff and svn up
but not svn commit (I basically disabled commit access for everyone for
the time being).
-- John T.
> -- John T.
>
> John Criswell wrote:
>
>> Dear LLVMers and Clangers,
>>
2005 Jan 07
1
[LLVMdev] Version Control
LLVMers,
The oversight group has been kicking around the idea of getting a better
version control system than CVS. The problem is, we're not quite sure
what "better" means. So, we thought we'd ask your opinions.
There are three options, unless someone strongly advocates another
solution:
1. Stay with CVS
2. Use Subversion
3. Use arch
Some of the things we're trying to
2006 Apr 02
0
Subversion mirrors of Asterisk, Zaptel and libpri rebuilt
Due to an error in the configuration of the mirroring tool we are using
to mirror the repositories from our internal commit server to the public
read-only mirror, the revision numbers were not being properly kept in
sync (so rev 14381 on the internal server was not the same as on the
mirror).
This problem has just been corrected, but it required rebuilding the
repositories on the mirror server