[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: To Merge or copy a feature branch?

From: Jan Hendrik <list.jan.hendrik_at_gmail.com>
Date: Wed, 16 Sep 2009 16:23:42 +0200

Concerning Re: To Merge or copy a feature bran
Les Mikesell wrote on 16 Sep 2009, 8:50, at least in part:

> I know the advice usually is to merge, but what if there have been
> enough changes in a branch that its history is really more
> representative than what is currently in trunk and its contents are
> what you want? Is there anything conceptually or philosophically
> wrong with deleting the trunk and copying the branch back to replace
> it?

I suppose the major notion is that the history is not lost, it's just
not accessible as easily in a (deleted) branch as in the continuous
trunk. For philiophical or ethical wrongs I would think it all depends
on how interesting or important history of either trunk or branch or
both or even in general is to the respective

Freedom quote:

     "Your friend Mr. Lincoln had his Taylors and Paines.
      So did every other man who ever tried to lift his thought up off the ground.
      Odds against them didn't stop those men, they were fools that way.
      All the good that ever came into this world came from fools with faith like that.
      You know that, Jeff. You can't quit now. Not you ...
      You didn't just have faith in Paine or any other living man.
      You had faith in something bigger than that.
      You had plain, decent, everyday common rightness.
      And this country could use some of that.
      Yeah, so could the whole cock-eyed world. A lot of it."
               -- Jean Arthur as Clarissa Saunders in
                  "Mr. Smith goes to Washington" by Frank Capra, 1939


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-09-16 16:27:50 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.