On 20050607T193722+, John Goerzen wrote:
On the other hand, as we've already established, all of this stuff
breaks if others are pulling your repo...
So don't do that.
I personally have one or two private darcs repos per project (the number
depends on if I work on it solely at home, solely
Hi!
John Goerzen [EMAIL PROTECTED] wrote:
While we're at it, I've never quite understood the utility of
amend-record, unrecord, etc. It seems that they would likely cause
major breakage if used on a repo that anyone else ever pulls or pushes
to/from. What is the usage scenario for them, and
On 2005-06-07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
While we're at it, I've never quite understood the utility of
amend-record, unrecord, etc. It seems that they would likely cause
major breakage if used on a repo that anyone else ever pulls or pushes
to/from. What is the usage
John == John Goerzen [EMAIL PROTECTED] writes:
John I guess I'm not sure what the utility over all this is, over
John simply recording a new patch that fixes things.
Well, since later you speak about dependencies, one use case of
unrecord is to break a patch in pieces, to minimize the
The commands like unrecord and amend-record are inevitable consequences of
decentralized revision control. If the commands did not exist, you could
easily achieve the same effect by creating a second repository with all
patches except the offending patch. That achieves unrecord. Then you
On Tue, Jun 07, 2005 at 10:52:59AM -0500, John Goerzen wrote:
On Tue, Jun 07, 2005 at 12:33:54PM -0300, [EMAIL PROTECTED] wrote:
The commands like unrecord and amend-record are inevitable consequences of
decentralized revision control. If the commands did not exist, you could
easily
* John Goerzen:
While we're at it, I've never quite understood the utility of
amend-record, unrecord, etc. It seems that they would likely cause
major breakage if used on a repo that anyone else ever pulls or pushes
to/from. What is the usage scenario for them, and what makes them so
very
On Tue, Jun 07, 2005 at 12:33:54PM -0300, zooko at zooko.com wrote:
The commands like unrecord and amend-record are inevitable consequences
of decentralized revision control. If the commands did not exist, you
could easily achieve the same effect by creating a second repository
John Goerzen [EMAIL PROTECTED] writes:
On 2005-06-03, David Roundy [EMAIL PROTECTED] wrote:
I'd say that there are three things that are good about darcs:
Maybe it's included in your first point, but low starting threshold
with lightweight installation and repository creation (no need to
On Sat, Jun 04, 2005 at 10:23:32PM +0900, Stephen J. Turnbull wrote:
Would it be that hard to simply spit out the list of patches in some
canonical text format all at once? That could be parsed, then a
controlling process could put up the GUI, then give commands to darcs
to actually do the
zooko == zooko [EMAIL PROTECTED] writes:
zooko P.S. A revision control tool is something which works only
zooko by interacting intimately with one or more skilled humans.
And a development process. One of the things that the arch community
spent a lot of time on (at least up until I
--- David Roundy [EMAIL PROTECTED] escribió:
I think your question is where darcs will be going once the conflictor code
is complete and well-tested? The long-time TODO list includes addition of
new patch types that will reduce the danger of conflicts in certain
situations (e.g. paragraphs
P.S. A revision control tool is something which works only by interacting
intimately with one or more skilled humans. Therefore analysis of the tool
by itself in the absence of its humans users is inherently a very limited
predictor of the tool's actual value. You, John Goerzen, are someone
On Thu, Jun 02, 2005 at 10:09:00AM -0300, [EMAIL PROTECTED] wrote:
P.S. A revision control tool is something which works only by interacting
intimately with one or more skilled humans. Therefore analysis of the tool
by itself in the absence of its humans users is inherently a very limited
On Wed, Jun 01, 2005 at 07:23:12PM +0200, Erik Bågfors wrote:
On 6/1/05, John Goerzen [EMAIL PROTECTED] wrote:
Incidentally, this bazaar-ng tutorial seems strikingly similar to darcs
in some areas, right down to bzr send...
http://www.bazaar-ng.org/tutorial.html
Of course, the whole
15 matches
Mail list logo
