On Jun 5, 2008, at 11:57 PM, root wrote:
>> I don't exactly understand these distributed control systems very
>> well, so hopefully this isn't an obvious question. Right now as I'm
>> working on symbolics I commonly have files from multiple branches
>> open
>> (symbolics-stable/backup, symbolic
This was not my point. My point was that if you use multiple branches
at the same time, your forced to have multiple physical branches of
the files, and while from my conversations on irc this may be
possible, its going to involve spending a bunch of effort to get what
we already have working aga
>I don't exactly understand these distributed control systems very
>well, so hopefully this isn't an obvious question. Right now as I'm
>working on symbolics I commonly have files from multiple branches open
>(symbolics-stable/backup, symbolics-current, calculus-old). I also
>have to frequently h
I don't exactly understand these distributed control systems very
well, so hopefully this isn't an obvious question. Right now as I'm
working on symbolics I commonly have files from multiple branches open
(symbolics-stable/backup, symbolics-current, calculus-old). I also
have to frequently have t
On Thu, 2008-06-05 at 16:27 -0700, Carl Witty wrote:
> On Jun 5, 3:28 pm, "Glenn H Tarbox, PhD" <[EMAIL PROTECTED]> wrote:
> > On Thu, 2008-06-05 at 14:23 -0700, Carl Witty wrote:
> > > As far as the second half of your response, I'm confused. The build
> > > system already understands chains whe
On Jun 5, 3:28 pm, "Glenn H Tarbox, PhD" <[EMAIL PROTECTED]> wrote:
> On Thu, 2008-06-05 at 14:23 -0700, Carl Witty wrote:
> > As far as the second half of your response, I'm confused. The build
> > system already understands chains where the output of one step is the
> > input to the next: the .
On Thu, 2008-06-05 at 14:23 -0700, Carl Witty wrote:
> On Jun 5, 1:10 pm, "Glenn H Tarbox, PhD" <[EMAIL PROTECTED]> wrote:
> > On Thu, 2008-06-05 at 12:41 -0700, Robert Bradshaw wrote:
> > > 1) Sage has a non-trivial build process for Cython files. When a .pyx
> > > file is changed, the .c file
On Thu, 2008-06-05 at 14:03 -0700, Robert Bradshaw wrote:
> On Jun 5, 2008, at 1:10 PM, Glenn H Tarbox, PhD wrote:
>
> >
> > On Thu, 2008-06-05 at 12:41 -0700, Robert Bradshaw wrote:
> >> I'll jump in and give some reasons that (for Sage) clones have
> >> advantages over branches.
> >>
> >> 1) Sa
On Jun 5, 2008, at 3:37 PM, root wrote:
>
>> In terms of using patches as a transport, its just a transport. I
>> think
>> it would be cleaner to import the branch as a branch and have final
>> merges into mainline branches controlled using current practice.
>> Patches in trac are, IMHO, clumsy
On Jun 5, 1:10 pm, "Glenn H Tarbox, PhD" <[EMAIL PROTECTED]> wrote:
> On Thu, 2008-06-05 at 12:41 -0700, Robert Bradshaw wrote:
> > 1) Sage has a non-trivial build process for Cython files. When a .pyx
> > file is changed, the .c file needs to be regenerated, as well as .so
> > file. Changing
>In terms of using patches as a transport, its just a transport. I think
>it would be cleaner to import the branch as a branch and have final
>merges into mainline branches controlled using current practice.
>Patches in trac are, IMHO, clumsy although in practice it probably
>doesn't matter much.
On Jun 5, 2008, at 1:10 PM, Glenn H Tarbox, PhD wrote:
>
> On Thu, 2008-06-05 at 12:41 -0700, Robert Bradshaw wrote:
>> I'll jump in and give some reasons that (for Sage) clones have
>> advantages over branches.
>>
>> 1) Sage has a non-trivial build process for Cython files. When a .pyx
>> file i
On Thu, 2008-06-05 at 15:40 -0400, didier deshommes wrote:
> On Thu, Jun 5, 2008 at 2:36 PM, Glenn H Tarbox, PhD <[EMAIL PROTECTED]> wrote:
> > So, I propose there's a misunderstanding of Hg and clone vs. branch. I
> > claim that branching is a trivial operation, switching between branches
> > is
On Thu, 2008-06-05 at 12:41 -0700, Robert Bradshaw wrote:
> On Jun 5, 2008, at 11:36 AM, Glenn H Tarbox, PhD wrote:
>
> > First, a joke... since I can't tell jokes, I offer:
> >
> > http://changelog.complete.org/posts/698-If-Version-Control-Systems-
> > were-Airlines.html
> >
> > Fortunately, I
On Thu, 2008-06-05 at 12:12 -0700, William Stein wrote:
> On Thu, Jun 5, 2008 at 11:36 AM, Glenn H Tarbox, PhD <[EMAIL PROTECTED]>
> wrote:
> > WARNING: its entirely up to you whether you wanna get into this... and
> > DVCS wars easily exceed politics and religion in the emotions and
> > vitriol
I don't really work directly with either branches or clones, but
instead have found Mercurial's queues to be the most effective way for
me to do Sage development. It is also well-suited for posting clean
patches on Trac for review.
--Mike
--~--~-~--~~~---~--~~
To
On Jun 5, 2008, at 11:36 AM, Glenn H Tarbox, PhD wrote:
> First, a joke... since I can't tell jokes, I offer:
>
> http://changelog.complete.org/posts/698-If-Version-Control-Systems-
> were-Airlines.html
>
> Fortunately, I won't be getting in to the Distributed Version Control
> Systems (DVCS) wa
On Thu, Jun 5, 2008 at 2:36 PM, Glenn H Tarbox, PhD <[EMAIL PROTECTED]> wrote:
> So, I propose there's a misunderstanding of Hg and clone vs. branch. I
> claim that branching is a trivial operation, switching between branches
> is fast, and that the entire point of DVCS is lost with the clone
> o
On Thu, Jun 5, 2008 at 11:36 AM, Glenn H Tarbox, PhD <[EMAIL PROTECTED]> wrote:
> WARNING: its entirely up to you whether you wanna get into this... and
> DVCS wars easily exceed politics and religion in the emotions and
> vitriol generated.
At least they aren't as bad as license wars. I think m
19 matches
Mail list logo
