Dustin Bachrach Blog - Latest Comments in Inline SCM: A Proposal For A Better SVN or Git

Re: Inline SCM: A Proposal For A Better SVN or Git

nike TN — Sat, 21 Apr 2012 04:34:01 -0000

http://www.tnpascherchine.com

Nike TN

Nike TN Requin

Nike TN Pas Cher

TN Pas Cher

Nike TN

TN Nike

Requin TN

t shirt

t shirt pas cher

t-shirt homme

Requin TN

TN Pas Cher

Nike tn 2012

tn foot locker

Re: Inline SCM: A Proposal For A Better SVN or Git

Cheap Air Jordan Shoes — Mon, 26 Mar 2012 05:09:14 -0000

22 morning, Xinhua News Agency reporters in the Bamako street and saw the sky guns, smoke dyed gray, the streets are full of heavily armed soldiers, many soldiers kept firing into the air, most people choose not hiding in the home dared to take to the streets.pingdeshijieluanle852

Re: Inline SCM: A Proposal For A Better SVN or Git

周雷 — Mon, 26 Mar 2012 01:16:54 -0000

Wholesale replica handbags is a Good site which Offer all kinds of high quality fashion handbags It's very good!
Replica Louis Vuitton handbags
replica Hermes handbags
replica prada handbags
replica Tory Burch handbags
replica gucci handbags
replica Miu Miu handbags
replica cartier handbags
replica balenciaga handbags
replica dior handbags
replica mulberry handbags
replica alexander wang handbags
replica goyard handbags
replica ysl handbags
replica celine handbags
replica lanvin handbags
replica chloe handbags
replica givenchy handbags

Re: Inline SCM: A Proposal For A Better SVN or Git

Air Max Ultimate — Thu, 09 Feb 2012 22:27:37 -0000

sont bien écrites. Je me demande comment je peux être averti à chaque fois un nouveau poste a été faite. Je suis abonné à votre flux rss qui devrait faire l'affaire! Avoir une agréable journée!

Re: Inline SCM: A Proposal For A Better SVN or Git

Jingling19900508 — Fri, 14 Oct 2011 02:29:32 -0000

Cheap NFL Jerseys, Authentic NFL Jerseys Cheap, NFL Jerseys Cheap, NFL Jerseys China, Cheap NFL Jerseys, Cheap Jerseys, NFL Jerseys UK, NFL Jerseys Cheap, NFL UK, NFL 2011

Re: Inline SCM: A Proposal For A Better SVN or Git

red laser — Tue, 01 Mar 2011 01:48:21 -0000

Someday they will come back.

Re: Inline SCM: A Proposal For A Better SVN or Git

Trein Parijs — Sat, 22 Jan 2011 04:52:29 -0000

Interesting post, came across this via searching on a search engine. We will look into this with our students and discuss.

Re: Inline SCM: A Proposal For A Better SVN or Git

Kobe Bryant Shoes — Wed, 14 Jul 2010 05:02:32 -0000

Nike Zoom LeBron James Soldier
The idea of friends upstairs is new and original,but I think to buy XX in the professinal outlet store is to our profit because things there have high quality &low price.When we are not rich,it can help us save 50-70% money there,why not buy them there?

Re: Inline SCM: A Proposal For A Better SVN or Git

baraniii — Mon, 01 Mar 2010 00:57:25 -0000

hello camila here.how are you.?oh very serious and boring issue you are talking about and right now i want to relax because these days i am busy doing preparation for security+ practice test.oh its really very interesting.

Re: Inline SCM: A Proposal For A Better SVN or Git

Guest — Fri, 05 Jun 2009 20:41:39 -0000

Interactive rebasing in git solves your problem.

Re: Inline SCM: A Proposal For A Better SVN or Git

Jason Skicewicz — Thu, 04 Jun 2009 16:35:53 -0000

This is a very interesting idea, and is very similar to an idea I had at one point that had to do with carving up the useful parts of the web, and attaching notes to blocks of web content. Its similar in that it is carving up the web at a finer granularity than bookmarks, which is what inline SCM is doing for source control. I think the usefulness would far outweigh how tedious it may become, and would encourage smaller commits, which is useful in its own right. I personally, check the diff on every file before I commit code to the repository to 1) come up with a descriptive commit message, and 2) to make sure I did not leave any debug code in what I am about to commit. So this whole process of looking at every block of changed code, would work extremely well in my workflow since I do it anyway.

I thought I would point out that your example is not exactly valid, although it is the way that many teams work. In a team that is following good process, all new features are developed in an entirely different branch, and are pulled in to your release branch as they are finalized / wanted / requested by biz. This way, the main branch, which is usually the trunk, only contains bug fixes and any approved features that were pulled in (nothing is developed in the main branch). I think what happened to the project that you are referencing, is that new features were developed in the main release branch. This should never be the case. The reason this happened, is because it was felt that these features would never be stripped out of the product, and would be present in the next release. A very bad assumption. This idea is very interesting because no teams (or very few) follow good version control practice. I mean, just take a look at how useful commit messages are on most projects.

In any case, this is a very good idea. One that I would love to help you build out =). You could easily build this on top of subversion or git without rewriting anything by essentially creating a markup language in the commit message itself. Sort of like the way InterTrac does it.