Re: [Monotone-devel] Re: cannot drop non-empty directory during branch update

2007-09-24 Thread J Decker
(true story) Okay turns out they weren't products of the build (even though no matter what they are, if you are developing a few bits of code in many places reversion is crazy annoying ) What if ... I start a project, add a few base things that are definatly in, but I'm adding a module

Re: [Monotone-devel] Re: cannot drop non-empty directory during branch update

2007-09-23 Thread Ethan Blanton
William Uther spake unto us the following wisdom: On 19/09/2007, at 12:51 PM, Ethan Blanton wrote: William Uther spake unto us the following wisdom: Hrm - if the files are auto-generated, then you should just delete them. You can re-generate them when you update back to this revision again.

Re: [Monotone-devel] Re: cannot drop non-empty directory during branch update

2007-09-20 Thread Brian May
William == William Uther [EMAIL PROTECTED] writes: William I actually think something maybe could change here in mtn. When a William directory should be dropped in an update, but it contains unversioned William files, rather than failing at that point the versioned files should

[Monotone-devel] Re: cannot drop non-empty directory during branch update

2007-09-18 Thread J Decker
Oh - yeah then it becomes a missing directory if I take the easy way out, and just rename the path... On 9/18/07, J Decker [EMAIL PROTECTED] wrote: I really really don't want to delete these files, I will very soon be back to work in this space... On 9/18/07, J Decker [EMAIL PROTECTED] wrote:

[Monotone-devel] Re: cannot drop non-empty directory during branch update

2007-09-18 Thread J Decker
I really really don't want to delete these files, I will very soon be back to work in this space... On 9/18/07, J Decker [EMAIL PROTECTED] wrote: mtn.EXE: switching to branch com.fortunet.altanik mtn.EXE: warning: cannot drop non-empty directory 'src/fut/flashdrive/flashdrivetester' mtn.EXE:

Re: [Monotone-devel] Re: cannot drop non-empty directory during branch update

2007-09-18 Thread William Uther
On 19/09/2007, at 9:39 AM, J Decker wrote: I really really don't want to delete these files, I will very soon be back to work in this space... On 9/18/07, J Decker [EMAIL PROTECTED] wrote: mtn.EXE: switching to branch com.fortunet.altanik mtn.EXE: warning: cannot drop non-empty directory

Re: [Monotone-devel] Re: cannot drop non-empty directory during branch update

2007-09-18 Thread Ethan Blanton
William Uther spake unto us the following wisdom: Hrm - if the files are auto-generated, then you should just delete them. You can re-generate them when you update back to this revision again. But you say you don't want to do that, so I assume that they have original data. In which

Re: [Monotone-devel] Re: cannot drop non-empty directory during branch update

2007-09-18 Thread Ethan Blanton
Ethan Blanton spake unto us the following wisdom: There is another possibility -- maybe they are simply expensive to generate. Several times in renaming directories in the Pidgin source tree, I've had to blow away quantities of object files which I would rather have kept, all things being

Re: [Monotone-devel] Re: cannot drop non-empty directory during branch update

2007-09-18 Thread William Uther
On 19/09/2007, at 12:51 PM, Ethan Blanton wrote: William Uther spake unto us the following wisdom: Hrm - if the files are auto-generated, then you should just delete them. You can re-generate them when you update back to this revision again. But you say you don't want to do that, so I

Re: [Monotone-devel] Re: cannot drop non-empty directory during branch update

2007-09-18 Thread Zack Weinberg
On 9/18/07, William Uther [EMAIL PROTECTED] wrote: I'm not sure this makes a real difference. Either you want to re- generate them or you don't. If you don't want to re-generate them then you should add them. I have nothing in particular to add to the rest of the discussion, but I want to