On Wed, Jan 08, 2014 at 03:12:08PM +0100, Michael Stahl wrote:
> On 08/01/14 14:27, Darryl L. Pierce wrote:
>
> > The problem is that it's been HOURS and Git hasn't finished cloning the
> > tree.
>
> > It's the third step which is taking forever to complete. I left it to
> > run overnight (10 hou
On 08/01/14 14:27, Darryl L. Pierce wrote:
> The problem is that it's been HOURS and Git hasn't finished cloning the
> tree.
> It's the third step which is taking forever to complete. I left it to
> run overnight (10 hours) and it never finished. I paused it, came to
> work, resumed it and it's s
On Wed, Jan 08, 2014 at 02:38:14PM +0100, Dan Horák wrote:
> in my experience it can take hours to clone large SVN repos (similar
> to 13k revisions in audacity), I usually use
> git svn clone --stdlayout
> but it should be equivalent to your procedure
>
> somewhere under .git you should see a fi
On Wed, 8 Jan 2014 08:27:42 -0500
"Darryl L. Pierce" wrote:
> I recently took over package maintenance for Audacity. So the first
> thing I want to do is clone their development tree, create a branch
> from the latest release and star tracking patches against it as
> needed. The Audacity team use
I recently took over package maintenance for Audacity. So the first
thing I want to do is clone their development tree, create a branch from
the latest release and star tracking patches against it as needed. The
Audacity team uses Subversion, while I prefer Git, so I attempted to use
Git to clone t
