Re: Successful full conversion

2017-12-18 Thread Mark Atwood
Where is this work keeping it's working archive?   On gitlab?

On Mon, Dec 18, 2017 at 3:25 PM Joseph Myers 
wrote:

> On Sat, 16 Dec 2017, Eric S. Raymond wrote:
>
> > Successful full conversion to a live git repo achieved.  Conversion
> > stuff pushed.
>
> Does it pass comparison (of both file content and permissions) of branch
> tips / tags, as an important test of whether there are any further bugs to
> resolve that show up that way, or is that test still to be done?
>
> > Jason, your filters script has a syntax error at line 32.  A lot of
>
> Looks like it should be using /bin/bash not /bin/sh.
>
> --
> Joseph S. Myers
> jos...@codesourcery.com
>
-- 

Mark Atwood
http://about.me/markatwood
+1-206-604-2198 Mobile & Signal


Re: Successful full conversion

2017-12-18 Thread Mark Atwood
Ok, thanks. I just get nervous about work thats not backed up.

On Mon, Dec 18, 2017, 4:47 PM Eric S. Raymond  wrote:

> Mark Atwood :
> > Where is this work keeping it's working archive?   On gitlab?
>
> The master is on grelber in my basement. Copies are synced by Joseph,
> another
> GCCer named Jason Merrill, and myself on snark.
> --
> http://www.catb.org/~esr/";>Eric S. Raymond
>
> My work is funded by the Internet Civil Engineering Institute:
> https://icei.org
> Please visit their site and donate: the civilization you save might be
> your own.
>
>
> --

Mark Atwood
http://about.me/markatwood
+1-206-604-2198 Mobile & Signal


Re: Good news, bad news on the repository conversion

2018-07-10 Thread Mark Atwood
ESR, how much for the memory expansion?  It sounds like we have some
volunteers to solve this problem with some money.

..m

On Tue, Jul 10, 2018 at 2:14 AM Aldy Hernandez  wrote:

> Wait, there's a pot of money for making SVN go away?  Sign me up!
> While we're at it, let's start one for TCL and dejagnu!
> On Mon, Jul 9, 2018 at 6:58 PM Jeff Law  wrote:
> >
> > On 07/09/2018 10:53 AM, Janus Weil wrote:
> > > 2018-07-09 18:35 GMT+02:00 Eric S. Raymond :
> > >> David Edelsohn :
> > >>>> The truth is we're near the bleeding edge of what conventional tools
> > >>>> and hardware can handle gracefully.  Most jobs with working sets as
> > >>>> big as this one's do only comparatively dumb operations that can be
> > >>>> parallellized and thrown on a GPU or supercomputer.  Most jobs with
> > >>>> the algorithmic complexity of repository surgery have *much* smaller
> > >>>> working sets.  The combination of both extrema is hard.
> > >>>
> > >>> If you come to the conclusion that the GCC Community could help with
> > >>> resources, such as the GNU Compile Farm or paying for more RAM, let
> us
> > >>> know.
> > >>
> > >> 128GB of DDR4 registered RAM would allow me to run conversions with my
> > >> browser up, but be eye-wateringly expensive.  Thanks, but I'm not
> > >> going to yell for that help
> > >
> > > I for one would certainly be happy to donate some spare bucks towards
> > > beastie RAM if it helps to get the GCC repo converted to git in a
> > > timely manner, and I'm sure there are other GCC
> > > developers/users/sympathizers who'd be willing to join in. So, where
> > > do we throw those bucks?
> > I'd be willing to throw some $$$ at this as well.
> > Jeff
> >
>
-- 

Mark Atwood
http://about.me/markatwood
+1-206-604-2198