Hello,
Na Wed, Aug 01, 2007 at 03:48:32PM -0700, David Roundy <[EMAIL PROTECTED]>
pisal(a):
> > * "pull" and "push" need to support XML. The structure should mirror
> > the human-readable output.
>
> Reasonable. This wouldn't happen unless we have a user, though. It's too
> easy to design a fe
On 8/1/07, Tommy Pettersson <[EMAIL PROTECTED]> wrote:
> DARCS_DONT_ESCAPE_ANYTHING turns off _all_ escaping. I couldn't
> find the ambiguousity in the manual, but that's probably because
> I wrote that part and is "blind" to it, so if you could please
> point it out or suggest a fix (now that the
On Wed, Aug 01, 2007 at 10:51:42PM +0200, Alexander Staubo wrote:
> On 8/1/07, David Roundy <[EMAIL PROTECTED]> wrote:
> > > I have spent a lot of time now driving Darcs from programs, and the
> > > minimal support for this idiom makes it painful. The XML format is not
> > > terribly useful to me s
On Wed, Aug 01, 2007 at 10:51:42PM +0200, Alexander Staubo wrote:
> I'm setting these:
>
> DARCS_DONT_COLOR=1
> DARCS_DONT_ESCAPE_TRAILING_SPACES=1
> DARCS_DONT_ESCAPE_ANYTHING=1
>
> I'm disabling the escaping because I don't need it -- I want the raw
> data. (Does ANYTHING imply TRAILING_SPACES?
On 8/1/07, David Roundy <[EMAIL PROTECTED]> wrote:
> > I have spent a lot of time now driving Darcs from programs, and the
> > minimal support for this idiom makes it painful. The XML format is not
> > terribly useful to me since it doesn't provide diffs. Darcs uses at
> > least three vaguely diffe
On 8/1/07, Tommy Pettersson <[EMAIL PROTECTED]> wrote:
> On Wed, Aug 01, 2007 at 02:28:44AM +0200, Alexander Staubo wrote:
> > I did consider doing an initial pull pass with --no-deps to see which
> > patches had dependencies, but that seems to have no effect, or perhaps
> > I have misunderstood th
On Wed, Aug 01, 2007 at 02:28:44AM +0200, Alexander Staubo wrote:
> On 8/1/07, David Roundy <[EMAIL PROTECTED]> wrote:
> > On Wed, Aug 01, 2007 at 12:43:44AM +0200, Alexander Staubo wrote:
> > > The only workaround I can think of is to run Darcs interactively, but
> > > that complicates things awfu
On Wed, Aug 01, 2007 at 02:28:44AM +0200, Alexander Staubo wrote:
> I did consider doing an initial pull pass with --no-deps to see which
> patches had dependencies, but that seems to have no effect, or perhaps
> I have misunderstood the meaning of this option:
>
> $ darcs pull --no-deps --dry-run
On 8/1/07, David Roundy <[EMAIL PROTECTED]> wrote:
> On Wed, Aug 01, 2007 at 12:43:44AM +0200, Alexander Staubo wrote:
> > The only workaround I can think of is to run Darcs interactively, but
> > that complicates things awfully, and I would like to avoid it. My
> > intent is to warn the user: "You
On Wed, Aug 01, 2007 at 12:43:44AM +0200, Alexander Staubo wrote:
> To start, I realized neither "pull" nor "changes" can provide patch
> hashes (well, changes can, but only in XML mode, which does not have
> diffs). At the moment I do one "pull --dry-run" to get all the pending
> patches so I can
On 7/26/07, David Roundy <[EMAIL PROTECTED]> wrote:
> On Thu, Jul 26, 2007 at 12:14:27AM +0200, Alexander Staubo wrote:
> > Actually, my question is similar to the FAQ (asked just recently on
> > this list) about how to retrieve a specific version of a file. Given a
> > patch -- specifically, one t
On Thu, Jul 26, 2007 at 04:17:25AM +0200, Alexander Staubo wrote:
> >And I'd like to have a "darcs query cat" subcommand that just dumps the
> >contents of a file, much like annotate, but a more focussed command, and
> >that doesn't add the annotations (which would make it faster).
>
> That would
At Wed, 25 Jul 2007 17:46:34 -0700,
David Roundy wrote:
> And I'd like to have a "darcs query cat" subcommand that just dumps the
> contents of a file, much like annotate, but a more focussed command, and
> that doesn't add the annotations (which would make it faster).
This is what the trac plugin
On 7/25/07, Alexander Staubo <[EMAIL PROTECTED]> wrote:
On 7/26/07, David Roundy <[EMAIL PROTECTED]> wrote:
> On Thu, Jul 26, 2007 at 02:32:22AM +0200, Alexander Staubo wrote:
> > I didn't know this. All right, good point, though there's the
> > additional snag: You cannot "get" from a partial re
On 7/26/07, David Roundy <[EMAIL PROTECTED]> wrote:
On Thu, Jul 26, 2007 at 02:32:22AM +0200, Alexander Staubo wrote:
> I didn't know this. All right, good point, though there's the
> additional snag: You cannot "get" from a partial repo -- you get this
> obscure error ("openBinaryFile: does not
On Thu, Jul 26, 2007 at 02:32:22AM +0200, Alexander Staubo wrote:
> On 7/26/07, David Roundy <[EMAIL PROTECTED]> wrote:
> >On Thu, Jul 26, 2007 at 12:14:27AM +0200, Alexander Staubo wrote:
> >> This is a small repo -- 3,500 files or around 24MB in total (excluding
> >> _darcs, which has 5,600 files
On 7/26/07, David Roundy <[EMAIL PROTECTED]> wrote:
On Thu, Jul 26, 2007 at 12:14:27AM +0200, Alexander Staubo wrote:
> This is a small repo -- 3,500 files or around 24MB in total (excluding
> _darcs, which has 5,600 files, or 64MB). Perhaps this operation is
> fairly quick with recently-checkpoi
On Thu, Jul 26, 2007 at 12:14:27AM +0200, Alexander Staubo wrote:
> On 7/25/07, David Roundy <[EMAIL PROTECTED]> wrote:
> >Locally cloning is pretty fast (should be blinding [...]
>
> Hm, I don't think so:
>
> $ time darcs get --partial trunk trunk.test
> Copying patch 2153 of 2153... done.
> App
On 7/25/07, David Roundy <[EMAIL PROTECTED]> wrote:
Locally cloning is pretty fast (should be blinding [...]
Hm, I don't think so:
$ time darcs get --partial trunk trunk.test
Copying patch 2153 of 2153... done.
Applying patch 2152 of 2152... done.
Finished getting.
real1m12.621s
user0
On Tue, Jul 24, 2007 at 09:02:04PM +0200, Alexander Staubo wrote:
> On 7/24/07, Eric Y. Kow <[EMAIL PROTECTED]> wrote:
> >> To do this, I need to find the contents of each side so that I can
> >> display them. The problem is that running "darcs pull --dry-run
> >> --verbose", for instance, does not
On 7/24/07, Eric Y. Kow <[EMAIL PROTECTED]> wrote:
> To do this, I need to find the contents of each side so that I can
> display them. The problem is that running "darcs pull --dry-run
> --verbose", for instance, does not yield sufficient information.
First: an apology; I have not read your mes
> To do this, I need to find the contents of each side so that I can
> display them. The problem is that running "darcs pull --dry-run
> --verbose", for instance, does not yield sufficient information.
First: an apology; I have not read your message thoroughly.
Second: would a sequence like this
I am writing a small tool for MacOS X to manage Darcs repos, as a
wrapper around the Darcs command-line tool -- it has a change-aware
repository browser, a visual differ, etc.
I am trying, at the moment, to implement a good user interface for
pulling and pushing patches. Given an upstream repo, t
23 matches
Mail list logo
