search for: _feel_

...ot entirely true. When working with git-svn, one has to be *very* careful about managing local branches. Because git-svn requires frequent rebases, sharing local branches with other developers becomes tricky. Not impossible, but you have to be very careful not to screw things up. It doesn't _feel_ like git, totally. It mostly does, until you hit the corner cases. -David

...hen working with git-svn, one has to be > *very* careful about managing local branches. Because git-svn requires > frequent rebases, sharing local branches with other developers becomes > tricky. Not impossible, but you have to be very careful not to screw > things up. It doesn't _feel_ like git, totally. It mostly does, until > you hit the corner cases. This is something I hadn't considered (the branch sharing), but it's a really good point. Since I'm not currently developing my changes in collaboration with other developers, I haven't experienced this. Howev...

The thing about this is that git-svn (un?)fortunately works so well that you can get all of these benefits with the main repo still in SVN. Hence, it is really a moot point regarding a switch to git for the main repo. E.g.: > Actually that's true today with svn. We have a ton of changes here we'd > like to submit but the process is really painful. Is there any difference from the

On Tue, Jul 28, 2015 at 08:01:21PM -0600, Chris Murphy wrote: > On Tue, Jul 28, 2015 at 6:17 PM, Timothy Murphy <gayleard at eircom.net> wrote: > > Warren Young wrote: > > > > > >> No, I am making the assumption that the vast majority of CentOS installs > >> are racked up in datacenters, VPS hosts, etc. > > > > Is that true, I wonder? >

With the approach of R 2.12.0: with mild apologies for re-opening this perennial issue: is there any hope, if appropriate patches are submitted, of adding a drop.levels argument (with default equal to FALSE to preserve backward compatibility/efficiency) to the subset function ... ? If not, would a patch to the documentation and/or the R FAQ be accepted? This does seem to be a continuing

Hello All, At my $WORK we have lots of in-house applications used to support the services we offer to customers and we deploy these to servers as RPMS. This works well for us except we have thousands of obsolete packages in our Yum repository that need to be cleaned up. What I would like to achieve is to keep the latest version + the last 3 revisions of a package and delete the older revisions.

i've released the first beta of my e-book converter-tool. you are invited to throw stones at it (and at me) if you like: > http://jaguarps.com "beta" is a compromise. i developed it on a mac, so that particular version is solid. but "alpha" would be a better label for the status of the windows and linux versions, so if you have one of _those_ machines, and you

I''ve been reading through the Rspec book to see if I missed any tricks, and the discussion of before block use for context setup in sec 12.6 struck me as interesting and something I had a knee-jerk reaction to. I think that when you are using nested examples to describe a context change it is bad practice to allow any example within that group to run outside of that context. This could