>> > [dev@lilydev:lilypond-git]$ git fsck
>> > Segmentation faultrectories: 45% (116/256)
>>
>> Ouch. I've never experienced such a thing with git. Maybe
>> something is broken with your installation? Does removing and
>> installing again help?
>
> Do you mean removing git itself? I'd like to
On Thu, Nov 14, 2019 at 9:58 PM David Nalesnik wrote:
>
> On Thu, Nov 14, 2019 at 9:49 PM Werner LEMBERG wrote:
> >
> >
> > >> There is git-fsck .
> > >>
> > >
> > > [dev@lilydev:lilypond-git]$ git fsck
> > > Segmentation faultrectories: 45% (116/256)
> >
> > Ouch. I've never experienced such a
On Thu, Nov 14, 2019 at 9:49 PM Werner LEMBERG wrote:
>
>
> >> There is git-fsck .
> >>
> >
> > [dev@lilydev:lilypond-git]$ git fsck
> > Segmentation faultrectories: 45% (116/256)
>
> Ouch. I've never experienced such a thing with git. Maybe something
> is broken with your installation? Does r
>> There is git-fsck .
>>
>
> [dev@lilydev:lilypond-git]$ git fsck
> Segmentation faultrectories: 45% (116/256)
Ouch. I've never experienced such a thing with git. Maybe something
is broken with your installation? Does removing and installing again
help?
Werner
Good god
On Thu, Nov 14, 2019 at 6:36 PM David Kastrup wrote:
>
> There is git-fsck .
>
[dev@lilydev:lilypond-git]$ git fsck
Segmentation faultrectories: 45% (116/256)
David Nalesnik writes:
> On Thu, Nov 14, 2019 at 10:21 AM Federico Bruni wrote:
>
>>
>>
>> Il giorno gio 14 nov 2019 alle 10:17, David Nalesnik
>> ha scritto:
>> > On Thu, Nov 14, 2019 at 9:34 AM David Nalesnik
>> > wrote:
>> >>
>> >> On Thu, Nov 14, 2019 at 9:23 AM David Kastrup wrote:
>> >
On Thu, Nov 14, 2019 at 10:21 AM Federico Bruni wrote:
>
>
> Il giorno gio 14 nov 2019 alle 10:17, David Nalesnik
> ha scritto:
> > On Thu, Nov 14, 2019 at 9:34 AM David Nalesnik
> > wrote:
> >>
> >> On Thu, Nov 14, 2019 at 9:23 AM David Kastrup wrote:
> >> >
> >> > Rather sounds like a dif
Il giorno gio 14 nov 2019 alle 10:17, David Nalesnik
ha scritto:
On Thu, Nov 14, 2019 at 9:34 AM David Nalesnik
wrote:
On Thu, Nov 14, 2019 at 9:23 AM David Kastrup wrote:
>
> Rather sounds like a different problem like a dead
server/connection.
> Try again?
Same result
And
On Thu, Nov 14, 2019 at 10:19 AM David Nalesnik
wrote:
>
> On Thu, Nov 14, 2019 at 10:17 AM David Nalesnik
> wrote:
> >
> > On Thu, Nov 14, 2019 at 9:34 AM David Nalesnik
> > wrote:
> > >
> > > On Thu, Nov 14, 2019 at 9:23 AM David Kastrup wrote:
> > > >
> > > > Rather sounds like a different
On Thu, Nov 14, 2019 at 10:17 AM David Nalesnik
wrote:
>
> On Thu, Nov 14, 2019 at 9:34 AM David Nalesnik
> wrote:
> >
> > On Thu, Nov 14, 2019 at 9:23 AM David Kastrup wrote:
> > >
> > > Rather sounds like a different problem like a dead server/connection.
> > > Try again?
> >
> > Same result.
On Thu, Nov 14, 2019 at 9:34 AM David Nalesnik wrote:
>
> On Thu, Nov 14, 2019 at 9:23 AM David Kastrup wrote:
> >
> > Rather sounds like a different problem like a dead server/connection.
> > Try again?
>
> Same result
And in fact any git command I try yields these fatal errors. (I tried
t
On Thu, Nov 14, 2019 at 9:23 AM David Kastrup wrote:
>
> David Nalesnik writes:
>
> > Hi all,
> >
> > I'm having difficulty getting my LilyDev machine to work with SSH.
> > I've followed the steps in the Contributor's Guide. Below is what
> > happens. I've included my config file, too.
> >
> >
David Nalesnik writes:
> Hi all,
>
> I'm having difficulty getting my LilyDev machine to work with SSH.
> I've followed the steps in the Contributor's Guide. Below is what
> happens. I've included my config file, too.
>
> If anyone can help, I'd be very grateful. I've got a patch to submit
> b
13 matches
Mail list logo