Patrick McCarty wrote Saturday, August 08, 2009 5:00 AM
On Fri, Aug 07, 2009 at 08:39:16PM -0700, Mark Polesky wrote:
Patrick McCarty wrote:
> I've just tested git's shallow cloning feature. It's pretty
> neat.
> :-)
>
> From what I can see, shallow clones would be okay for *casual*
> co
Le vendredi 07 août 2009 à 21:00 -0700, Patrick McCarty a écrit :
> Personally, I browse git history on the command line quite often when
> working with LilyPond.
So do I, or sometimes with gitk.
There are already many Git features to master for daily use, I'm not
keen on adding to the CG the sha
On Fri, Aug 07, 2009 at 08:39:16PM -0700, Mark Polesky wrote:
>
> Patrick McCarty wrote:
>
> > I've just tested git's shallow cloning feature. It's pretty neat.
> > :-)
> >
> > From what I can see, shallow clones would be okay for *casual*
> > contributors that are only sending patches based on
Patrick McCarty wrote:
> I've just tested git's shallow cloning feature. It's pretty neat.
> :-)
>
> From what I can see, shallow clones would be okay for *casual*
> contributors that are only sending patches based on the tip of master.
>
> However, since git history is limited to the depth of
On Mon, Aug 03, 2009 at 06:45:38PM -0700, Graham Percival wrote:
> On Mon, Aug 03, 2009 at 06:18:20PM -0700, Mark Polesky wrote:
> >
> > Graham Percival wrote:
> >
> > > If you do restart, try the
> > > git clone --depth 1 git://URL
> > > method. (the CG will probably be updated to use this me
Trevor Daniels wrote:
> Something must have happened between the last
> time git worked and the first time it failed.
> Anything you did during that time is a suspect.
The only other things I can imagine:
1) my anti-virus software might have done something
2) my security might have been compromi
Mark Polesky wrote Tuesday, August 04, 2009 9:23 AM
Does anyone know -- is there any harm in just generating a new
SSH key pair?
No harm at all.
I think my modem gives me a different IP address
from time to time.
It (well, your ISP) will - that's normal.
I could be making that up, and I
On Tue, Aug 04, 2009 at 01:23:11AM -0700, Mark Polesky wrote:
> Does anyone know -- is there any harm in just generating a new
> SSH key pair?
Absolutely no problems. Go ahead.
> I think my modem gives me a different IP address
> from time to time. I could be making that up, and I don't know
> i
Does anyone know -- is there any harm in just generating a new
SSH key pair? I think my modem gives me a different IP address
from time to time. I could be making that up, and I don't know
if that would even affect the SSH stuff. But I'm willing to try
anything at this point. Would generating a ne
On Mon, Aug 03, 2009 at 06:18:20PM -0700, Mark Polesky wrote:
>
> Graham Percival wrote:
>
> > If you do restart, try the
> > git clone --depth 1 git://URL
> > method. (the CG will probably be updated to use this method in a
> > week or so)
>
> it seems that this method is not suitable for de
Graham Percival wrote:
> If you do restart, try the
> git clone --depth 1 git://URL
> method. (the CG will probably be updated to use this method in a
> week or so)
Graham,
it seems that this method is not suitable for developers with
push access. You can't push from it -- see below.
- Mark
Mark Polesky wrote Monday, August 03, 2009 11:38 PM
Trevor Daniels wrote:
These commands will fail. The correct command is
$ git reset --hard origin/master
It gets up to 50%, then crashes:
Checking out files: 50% (963/1926)
(here the Windows error box pops up)
Once I close the pop-up,
Trevor Daniels wrote:
> These commands will fail. The correct command is
>
> $ git reset --hard origin/master
It gets up to 50%, then crashes:
Checking out files: 50% (963/1926)
(here the Windows error box pops up)
Once I close the pop-up, the line changes to:
fatal: Could not reset index
Mark Polesky wrote Monday, August 03, 2009 4:25 PM
Graham Percival wrote:
What does:
git reset --hard origin
or
git reset --hard origin master
do? I'd expect one of those to set you to a working state. (NB:
by "I'd expect", I mean "as a user, I think the program should do
this". Unfortu
Graham Percival wrote:
> What does:
> git reset --hard origin
> or
> git reset --hard origin master
> do? I'd expect one of those to set you to a working state. (NB:
> by "I'd expect", I mean "as a user, I think the program should do
> this". Unfortunately, as somebody who's been fighting
On Mon, Aug 03, 2009 at 08:54:58AM +0100, Trevor Daniels wrote:
>
> Mark Polesky wrote Monday, August 03, 2009 2:30 AM
>>
> 3.
>> git gui/Repository/Verify Database
>> With that, I get:
>> Error: Command Failed
>> git-fsck-objects.exe has encountered a problem and needs to close.
>> We are sorry fo
Mark Polesky wrote Monday, August 03, 2009 2:30 AM
Mark Polesky wrote:
> 199.232.41.69 ssh-rsa B3NzaC1yc2E ...
>
> It's the public key of the Savannah server. In
> case you've lost it, I've attached one.
My copy of the public key looks fine.
Any other ideas?
Not shots in the dar
Mark Polesky wrote:
> > 199.232.41.69 ssh-rsa B3NzaC1yc2E ...
> >
> > It's the public key of the Savannah server. In
> > case you've lost it, I've attached one.
>
> My copy of the public key looks fine.
Any other ideas?
I'm thinking of removing my entire lilypond repo and starting
ov
Trevor Daniels wrote:
> > $ git fetch
> > The authenticity of 'git.sv.gnu.org (199.232.41.69)' can't be established.
> > RSA key fingerprint is
> > Are you sure you want to continue connecting (yes/no)?
>
> This means the known-hosts file has been deleted
> or corrupted or can't be found.
Mark Polesky wrote Sunday, August 02, 2009 10:03 PM
So I did git fetch and got this:
$ git fetch
The authenticity of 'git.sv.gnu.org (199.232.41.69)' can't be
established.
RSA key fingerprint is
Are you sure you want to continue connecting (yes/no)?
This means the known-hosts file ha
So I did git fetch and got this:
$ git fetch
The authenticity of 'git.sv.gnu.org (199.232.41.69)' can't be established.
RSA key fingerprint is
Are you sure you want to continue connecting (yes/no)?
and it doesn't matter how I respond. It always goes into an endless loop.
I always have to f
Mark Polesky wrote Sunday, August 02, 2009 1:43 AM
Trevor Daniels wrote:
> Error reading commits:
> child killed: unknown signal
I've never seen this error message, but it
suggests a problem with the git repo. Try
verifying the database. git gui/Repository/Verify Database
With that, I get
Trevor Daniels wrote:
> > Error reading commits:
> > child killed: unknown signal
>
> I've never seen this error message, but it
> suggests a problem with the git repo. Try
> verifying the database. git gui/Repository/Verify Database
With that, I get:
Error: Command Failed
git-fsck-objects.e
Mark Polesky wrote Saturday, August 01, 2009 9:09 PM
Patrick McCarty wrote:
> $ git pull ssh://sv/srv/git/lilypond.git master
> fatal: The remote end hung up unexpectedly
Well, that URI is kind of bogus. :-)
It worked fine yesterday.
It works fine here today too. That's not the problem
Patrick McCarty wrote:
> > $ git pull ssh://sv/srv/git/lilypond.git master
> > fatal: The remote end hung up unexpectedly
>
> Well, that URI is kind of bogus. :-)
It worked fine yesterday.
> This should work:
>
> $ git pull git://git.sv.gnu.org/lilypond.git master
No luck. Same fatal mess
On Sat, Aug 01, 2009 at 12:05:35PM -0700, Mark Polesky wrote:
>
> I'm getting this:
>
> $ git pull ssh://sv/srv/git/lilypond.git master
> fatal: The remote end hung up unexpectedly
Well, that URI is kind of bogus. :-)
This should work:
$ git pull git://git.sv.gnu.org/lilypond.git master
__
I'm getting this:
$ git pull ssh://sv/srv/git/lilypond.git master
fatal: The remote end hung up unexpectedly
While waiting for the response, 2 git.exe instances appear in
the task manager, and then both crash. Any ideas why?
It was working fine yesterday. Using Mingw32 bash on XP.
Thanks.
- Ma
27 matches
Mail list logo
