On Monday 30 March 2009, Sebastian Kuzminsky wrote:
> play around in your own sandbox, building up and tearing down stuff,
> testing things, all outside the attention of other developers.
Scenario 1 - Each developer runs their own VCS outside of Sourceforge
adding "features", fixing bugs and gene
paul_c wrote:
> On Sunday 29 March 2009, Chris Morley wrote:
>> I was trying to bring the cl_v7124_branch up to date with trunk so I could
>> use it to continue some experimental programs rather then start a new
>> branch.
>
> The whole thing is experimental, so trunk is as good a place as any.
T
On Sunday 29 March 2009, Chris Morley wrote:
> Sorry about the 100 commits and the failed compile (love that blame list :)
You are not to blame for a misconfigured CVS repository - One commit should
only generate a single message and show diffs of files that *you* changed.
> I was trying to brin
> > The deb builds in Trunk are still failing on all platforms. Looks like
> > /usr/bin/pcnconf was added to the "make install" target, but not to any
> > of the debian packages.
>
On Sun, Mar 29, 2009 at 06:23:41AM +, Chris Morley wrote:
> How do I fix that?
In debian/emc2.files.in, just
> Date: Sat, 28 Mar 2009 20:30:48 -0600
> From: s...@highlab.com
> To: emc-developers@lists.sourceforge.net
> Subject: Re: [Emc-developers] sorry about the 100 commits...
>
> Chris Morley wrote:
> > Sorry about the 100 commits and the failed compile (love that blame lis
Chris Morley wrote:
> Sorry about the 100 commits and the failed compile (love that blame list :)
> I was trying to bring the cl_v7124_branch up to date with trunk so I could
> use it to continue some experimental programs rather then start a new branch.
> I guess it didn't work quite right as my
Sorry about the 100 commits and the failed compile (love that blame list :)
I was trying to bring the cl_v7124_branch up to date with trunk so I could
use it to continue some experimental programs rather then start a new branch.
I guess it didn't work quite right as my commit went to truck.
