On Mon, 2008-07-07 at 11:57 -0700, Sean Chittenden wrote:
> >> Is there any reason to nuke 'em? -sc
> >
> > I was thinking more along the lines of whether there is any reason
> > to keep them.
> >
> > My thinking in getting rid of them is the repository will have less
> > clutter (less code) a
Is there any reason to nuke 'em? -sc
I was thinking more along the lines of whether there is any reason
to keep them.
My thinking in getting rid of them is the repository will have less
clutter (less code) and check out times will be significantly
reduced. Since they are now dead code,
Sean Chittenden wrote:
If you can go back a tag the prior release, that would be good, but
since you already committed there no reason to make a big fuss about
it (as long as everything is still working! ;) We can just move
forward from here.
Tagged.
Does anyone mind if I clean out the old b
If you can go back a tag the prior release, that would be good, but
since you already committed there no reason to make a big fuss about
it (as long as everything is still working! ;) We can just move
forward from here.
Tagged.
Does anyone mind if I clean out the old branches in the repository?
If you can go back a tag the prior release, that would be good, but
since you already committed there no reason to make a big fuss about
it (as long as everything is still working! ;) We can just move
forward from here.
Tagged.
Does anyone mind if I clean out the old branches in the reposit
On Thu, 2008-07-03 at 11:01 -0700, Sean Chittenden wrote:
> >>> Before we do that though I was wondering what others thought about
> >>> of
> >>> switching to Git?
> >>
> >> Well, I know git is the new cool think in town. But I'm on
> >> Windows, and
> >> love TortoiseSvn, so I don't have any
On Jul 3, 2:01 pm, Sean Chittenden <[EMAIL PROTECTED]> wrote:
> git is demon spawn - don't get sucked into the ill-thought-out fad.
I think that's a bit overstated. From what I understand the primary
difference is the backend storage. Git stores an snapshot and Hg
stores a delta. Perhaps Mackal
On Jul 3, 2008, at 14:01, Sean Chittenden wrote:
Before we do that though I was wondering what others thought
about of
switching to Git?
Well, I know git is the new cool think in town. But I'm on
Windows, and
love TortoiseSvn, so I don't have any motivation to move to git
(lousy
window
Eventually, some sort of distributed source code management would be
nice. I think it makes sense for open source projects for a lot of
reasons. That being said, I think it is more important to use a SCM
that is compatible with the environment of the current contributors.
The revival of the gem by
Eventually, some sort of distributed source code management would be
nice. I think it makes sense for open source projects for a lot of
reasons. That being said, I think it is more important to use a SCM
that is compatible with the environment of the current contributors.
The revival of the gem by
Before we do that though I was wondering what others thought about
of
switching to Git?
Well, I know git is the new cool think in town. But I'm on
Windows, and
love TortoiseSvn, so I don't have any motivation to move to git
(lousy
windows support and no gui). I suppose it was easy to hav
On Jul 3, 1:15 pm, Charlie Savage <[EMAIL PROTECTED]> wrote:
> Hi Trans,
>
> > Sorry I've been out of the loop for a bit. I've been working on some
> > other projects.
>
> > I just emailed Charlie about working with him to get a new release
> > out. How do we want to handle this? Should we tag th
Hi Trans,
Sorry I've been out of the loop for a bit. I've been working on some
other projects.
I just emailed Charlie about working with him to get a new release
out. How do we want to handle this? Should we tag the current version
and allow the patches on trunk? Or create a branch and apply th
Hi all,
Sorry I've been out of the loop for a bit. I've been working on some
other projects.
I just emailed Charlie about working with him to get a new release
out. How do we want to handle this? Should we tag the current version
and allow the patches on trunk? Or create a branch and apply the
pa
14 matches
Mail list logo
