Re: [Monotone-devel] Monotone-viz and repository structure.
Hi Hendrik, Am Sun, 21 Feb 2010 15:57:57 -0500 schrieb hend...@topoi.pooq.com: On Sun, Feb 21, 2010 at 03:35:42PM -0500, hend...@topoi.pooq.com wrote: I have my own copy of the monotone repository. At least I think I do. It seems to sync properly when I pull. But I' trying to obtain monotone-viz. It doesn't seem to be in my repository, Is this just an accident of history, that I failed to specify the branch when I pulled monotone initially? Or is it, and should it be, in a completely separate repository? It is in the branch net.venge.monotone-viz (and some subbranches thereof) in the monotone repository served at monotone.ca. Depending on the pattern you are using (see mtn ls vars database) this branch name might have never matched during pull for you. Thomas ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
Re: [Monotone-devel] [ANN] guitone-1.0rc1 released
On 2010-02-15 15:06, I wrote: I'll try and prepare a Windows binary in the next couple of days, but probably won't get to that before Wednesday, so if you want to help out, drop me a note. A binary for Mac OS X should be come shortly as well. Both, the Mac and the Win32 binaries, are now online and can be downloaded from https://guitone.thomaskeller.biz/g/download. Thomas. -- GPG-Key 0x160D1092 | tommyd3...@jabber.ccc.de | http://thomaskeller.biz Please note that according to the EU law on data retention, information on every electronic information exchange might be retained for a period of six months or longer: http://www.vorratsdatenspeicherung.de/?lang=en signature.asc Description: OpenPGP digital signature ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
Re: [Monotone-devel] Monotone-viz and repository structure.
On Mon, Feb 22, 2010 at 11:06:13AM +0100, Thomas Moschny wrote: Hi Hendrik, Am Sun, 21 Feb 2010 15:57:57 -0500 schrieb hend...@topoi.pooq.com: On Sun, Feb 21, 2010 at 03:35:42PM -0500, hend...@topoi.pooq.com wrote: I have my own copy of the monotone repository. At least I think I do. It seems to sync properly when I pull. But I' trying to obtain monotone-viz. It doesn't seem to be in my repository, Is this just an accident of history, that I failed to specify the branch when I pulled monotone initially? Or is it, and should it be, in a completely separate repository? It is in the branch net.venge.monotone-viz (and some subbranches thereof) in the monotone repository served at monotone.ca. Depending on the pattern you are using (see mtn ls vars database) this branch name might have never matched during pull for you. Thanks. I was more-or-less asking about best practices rather than trying to solve a problem. If it is in the same repository at headquarters, it makes some to be consistent and put it in the same repository here. But I am starting to suspect that it really doesn't matter much. -- hendrik ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] How to split a project
Let's say I have some code checked in along some branch. Over the year it has evolved so that it has become two separate programs, that don't share any code any more, and make sense to develop independently. Evidently, it makes sense to make two branches, one for each program. The obvious way is just start new branch(es) and in each branch delete all the files now belonging to the other. BUT. If years down the line, someone wants to include both these programs into another project, I don't want the merge saying, let's merge all these changes. Looky here, all the files of each branch have been deleted on the other. There's nothing left! And that someone mysteriously end up with no files instaed of all the files. Is there a better way to split a project? If not, should there be? Or, Am I worrying about nothing? -- hendrik ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
Re: [Monotone-devel] [ANN] guitone-1.0rc1 released
I tried the Windows binary, and I get a message that says: This application has failed to start because libgccc_s_dw2-1.dll was not found. Something missing from the build? Howard At 05:37 AM 2/22/2010, Thomas Keller wrote: On 2010-02-15 15:06, I wrote: I'll try and prepare a Windows binary in the next couple of days, but probably won't get to that before Wednesday, so if you want to help out, drop me a note. A binary for Mac OS X should be come shortly as well. Both, the Mac and the Win32 binaries, are now online and can be downloaded from https://guitone.thomaskeller.biz/g/download. Thomas. -- GPG-Key 0x160D1092 | tommyd3...@jabber.ccc.de | http://thomaskeller.biz Please note that according to the EU law on data retention, information on every electronic information exchange might be retained for a period of six months or longer: http://www.vorratsdatenspeicherung.de/?lang=en ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
Re: [Monotone-devel] [ANN] guitone-1.0rc1 released
Am 22.02.10 23:09, schrieb Howard Spindel: I tried the Windows binary, and I get a message that says: This application has failed to start because libgccc_s_dw2-1.dll was not found. Something missing from the build? Hrm... apparently, thanks for the pointer. Last time I did a win32 package this was not needed, but newer Qt versions need an updated mingw with gcc 4.4 and apparently something is missing along these lines. What I've read so far on the net this dll is packaged in gcc-core-4.4.0-mingw32-dll.tar.gz, so if you don't want to wait until tomorrow, check if downloading this package from http://bit.ly/b8jYey fixes this problem. I think I have to dig out my old friend the dependency walker anyways, hopefully this still runs on the Windows 7 VM where I've build the binary. Thanks again for the pointer, Thomas. -- GPG-Key 0x160D1092 | tommyd3...@jabber.ccc.de | http://thomaskeller.biz Please note that according to the EU law on data retention, information on every electronic information exchange might be retained for a period of six months or longer: http://www.vorratsdatenspeicherung.de/?lang=en signature.asc Description: OpenPGP digital signature ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
Re: [Monotone-devel] How to split a project
There's the more immediate case, even, of discovering that part of one project is really a module that should be shareable - you'd like to pull it out into its own branch, delete files on both sides, and then merge_into_dir the module's branch. Alas, since they share a common parent, this is forbidden. I have a rough understanding that there's some more-than-trivial complication with making that possible, but I'm not clear on what it is. Judson On Mon, Feb 22, 2010 at 6:45 AM, hend...@topoi.pooq.comhendrik wrote: Let's say I have some code checked in along some branch. Over the year it has evolved so that it has become two separate programs, that don't share any code any more, and make sense to develop independently. Evidently, it makes sense to make two branches, one for each program. The obvious way is just start new branch(es) and in each branch delete all the files now belonging to the other. BUT. If years down the line, someone wants to include both these programs into another project, I don't want the merge saying, let's merge all these changes. Looky here, all the files of each branch have been deleted on the other. There's nothing left! And that someone mysteriously end up with no files instaed of all the files. Is there a better way to split a project? If not, should there be? Or, Am I worrying about nothing? -- hendrik ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
Re: [Monotone-devel] How to split a project
The other method is to make a quick commit with --branch=program1 branch pivot_root program1's new root directory old_root - will put all files in the root into old_root and make the program directories current. You can then use mtn drop to drop old_root. this is bad, in that you cannot propagate to this new changes to the common trunk... but if you're really just making a new trunk, but want to retain the revision history, as long as you do not ever propagate between these, it's not so bad. Oh I guess the more important direction is that you cannot propagate from the pivoted branch to the main, as it would inherit the pivot. I really this the pivot point should be handled differently maybe someone could make a new operation that is a sensible 'make this point in a branch a seperate branch, which I can propagate to and from the main trunk (only changes to files within that branch basically)' On Mon, Feb 22, 2010 at 6:45 AM, hend...@topoi.pooq.comhendrik wrote: Let's say I have some code checked in along some branch. Over the year it has evolved so that it has become two separate programs, that don't share any code any more, and make sense to develop independently. Evidently, it makes sense to make two branches, one for each program. The obvious way is just start new branch(es) and in each branch delete all the files now belonging to the other. BUT. If years down the line, someone wants to include both these programs into another project, I don't want the merge saying, let's merge all these changes. Looky here, all the files of each branch have been deleted on the other. There's nothing left! And that someone mysteriously end up with no files instaed of all the files. Is there a better way to split a project? If not, should there be? Or, Am I worrying about nothing? -- hendrik ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
