sm-discuss AT lists.ibiblio.org
Subject: Public SourceMage Discussion List
List archive
- From: Jeremy Blosser <jblosser-smgl AT firinn.org>
- To: sm-discuss AT lists.ibiblio.org
- Subject: Re: [SM-Discuss] scm next steps
- Date: Tue, 9 May 2006 09:07:04 -0500
On May 09, David Kowis [dkowis AT shlrm.org] wrote:
> Jeremy Blosser (emrys) wrote:
> <snip>
> > I also have to mention: alley_cat reported what looked like a git bug
> > yesterday regarding an operation taking too long to run, and it got fixed
> > for us today. Oh, and the guy that downloaded our grimoire tree and
> > found/fixed the bug for us minutes after hearing of the issue was one
> > Linus
> > Torvalds. :-)
> >
>
> Now if that's not a good reason to use git, I don't know what is ;)
I guess the objective important thing to me there is the support we're
getting. #git is a very friendly channel. We have been asking a lot of
questions in there, and they're giving us the pointers we need. One of
them has even been camping #sourcemage for a while now and answering
questions there too, and has gone off and written a p4 importer that
auto-tags git with every p4 changeset (so you can checkout the git repo to
match any changeset). Having a bug fixed that fast (and by a demigod no
less) is just icing. They're actually at a period right now where they're
seeing a fair bit more use beyond the original plans for the kernel and
they are very interested in hearing how it works out for other workflows,
especially people using a centralized model, and making it work even
better. Linus in particular is pushing for feedback so they can improve
the tutorial-type docs for each normal use case.
Compare this to #svn who apparently didn't want to believe e-type when he
went in there to ask about the disk space requirements. ;-P I'll probably
try them later today on the same question, but it looks like it's simple
block size math for the number of .svn dirs/files they need...
Attachment:
pgpEz3JybWOcn.pgp
Description: PGP signature
-
Re: [SM-Discuss] scm next steps
, (continued)
-
Re: [SM-Discuss] scm next steps,
Arwed von Merkatz, 05/04/2006
-
Re: [SM-Discuss] scm next steps,
Eric Sandall, 05/04/2006
-
Re: [SM-Discuss] scm next steps,
Jeremy Blosser (emrys), 05/04/2006
- Re: [SM-Discuss] scm next steps, Eric Sandall, 05/04/2006
-
Re: [SM-Discuss] scm next steps,
Jeremy Blosser (emrys), 05/04/2006
-
Re: [SM-Discuss] scm next steps,
Eric Sandall, 05/04/2006
-
Re: [SM-Discuss] scm next steps,
Jeremy Blosser (emrys), 05/04/2006
- Re: [SM-Discuss] scm next steps, Arwed von Merkatz, 05/04/2006
- Re: [SM-Discuss] scm next steps, Jeremy Blosser (emrys), 05/06/2006
- Re: [SM-Discuss] scm next steps, Eric Sandall, 05/06/2006
-
Re: [SM-Discuss] scm next steps,
Jeremy Blosser (emrys), 05/08/2006
-
Re: [SM-Discuss] scm next steps,
David Kowis, 05/09/2006
- Re: [SM-Discuss] scm next steps, Jeremy Blosser, 05/09/2006
- Re: [SM-Discuss] scm next steps, Jeremy Blosser (emrys), 05/12/2006
-
Re: [SM-Discuss] scm next steps,
David Kowis, 05/09/2006
- Re: [SM-Discuss] scm next steps, Jeremy Blosser (emrys), 05/13/2006
-
Re: [SM-Discuss] scm next steps,
Jeremy Blosser (emrys), 05/20/2006
-
Re: [SM-Discuss] scm next steps,
Jaka Kranjc, 05/20/2006
-
Re: [SM-Discuss] scm next steps,
Andraž "ruskie" Levstik, 05/20/2006
- Re: [SM-Discuss] scm next steps, Jeremy Blosser, 05/20/2006
- Re: [SM-Discuss] scm next steps, Eric Sandall, 05/20/2006
-
Re: [SM-Discuss] scm next steps,
Andraž "ruskie" Levstik, 05/20/2006
-
Re: [SM-Discuss] scm next steps,
Eric Sandall, 05/20/2006
-
Re: [SM-Discuss] scm next steps,
Arwed von Merkatz, 05/20/2006
- Re: [SM-Discuss] scm next steps, seth, 05/20/2006
-
Re: [SM-Discuss] scm next steps,
Arwed von Merkatz, 05/20/2006
-
Re: [SM-Discuss] scm next steps,
Jaka Kranjc, 05/20/2006
-
Re: [SM-Discuss] scm next steps,
Arwed von Merkatz, 05/04/2006
Archive powered by MHonArc 2.6.24.