Re: [Monotone-devel] Initially creating a branch without committing changes?
In message <[EMAIL PROTECTED]> on Tue, 11 Sep 2007 09:14:29 +1000, Brian May <[EMAIL PROTECTED]> said: bam> > "Richard" == Richard Levitte <[EMAIL PROTECTED]> writes: bam> bam> ludovic> In the sense that "mtn approve h:foo.bar.cvs --branch bam> ludovic> foo.bar" does the same thing, that is :) Or am I bam> ludovic> mistaken? bam> bam> Richard> Think twice before you do that, it could be a bit bam> Richard> surprising (I know, I did it on the nvm branch ;-)). bam> bam> As somebody who never has fully explored branches in detail yet, why bam> can that produce surprising results? bam> bam> Is there any difference between: bam> bam> mtn cert h:foo.bar.cvs branch foo.bar bam> bam> and bam> bam> mtn approve h:foo.bar.cvs --branch foo.bar bam> bam> ??? Never mind, there's apparently been a change in semantics that I didn't notice... Cheers, Richard - Please consider sponsoring my work on free software. See http://www.free.lp.se/sponsoring.html for details. -- Richard Levitte [EMAIL PROTECTED] http://richard.levitte.org/ "When I became a man I put away childish things, including the fear of childishness and the desire to be very grown up." -- C.S. Lewis ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: cvs_import feature sponsored
Markus Schiltknecht wrote: Dear monotone hackers, I'm happy to announce that I've recently signed a contract with MQSoftware, who sponsors me for finishing my cvs_import rewrite. I wish to thank Kelly F. Hickel for making this possible, and I'm looking forward to contribute to their and monotone's success. Wonderful news, congratulations! It probably does not require mentioning, but if possible of course I'd encourage you to do this with a clean enough interface to monotone that other projects can reuse it. While I'm always pleased to have monotone be "best" at something, extracting latent structure from a CVS archive is as you know research-grade inference work, and if you can condense what you learn into a reusable tool it'll probably have greater visibility and longevity. -graydon ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
Re: [Monotone-devel] monotone Hacking
On 10/09/2007, at 7:49 PM, Thomas Keller wrote: Hi all! I've noticed that the changelog some people use for monotone is not quite "GNU-style". I'm sure you all hacked stuff longer than me, so you can correct me at any time, but aren't we forced to use some kind of GNU-style syntax to make it easier to create a ChangeLog file afterwards (for whatever distributions need that)? If not, everybody is - of course - free to use whatever format they do like. I don't like to start a bikeshed discussion here, I just want to be clear. I think it would also be a good idea to include the rules of whatever consense we find here in HACKING. I think including the rules in HACKING would be a good idea. Out of interest, who actually converts log messages directly to change logs? I would have thought that most people who distribute Monotone would find the more abstract changes described in the NEWS file more relevant. Will:-} ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
Re: [Monotone-devel] Initially creating a branch without committing changes?
> "Richard" == Richard Levitte <[EMAIL PROTECTED]> writes: ludovic> In the sense that "mtn approve h:foo.bar.cvs --branch ludovic> foo.bar" does the same thing, that is :) Or am I ludovic> mistaken? Richard> Think twice before you do that, it could be a bit Richard> surprising (I know, I did it on the nvm branch ;-)). As somebody who never has fully explored branches in detail yet, why can that produce surprising results? Is there any difference between: mtn cert h:foo.bar.cvs branch foo.bar and mtn approve h:foo.bar.cvs --branch foo.bar ??? -- Brian May <[EMAIL PROTECTED]> ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
Re: [Monotone-devel] cvs_import feature sponsored
On Sat, Sep 08, 2007 at 08:49:29PM +0200, Markus Schiltknecht wrote: > Dear monotone hackers, > > I'm happy to announce that I've recently signed a contract with > MQSoftware, who sponsors me for finishing my cvs_import rewrite. I wish > to thank Kelly F. Hickel for making this possible, and I'm looking > forward to contribute to their and monotone's success. How cool! Looking forward to seeing what you come up with. -- Nathaniel -- Details are all that matters; God dwells there, and you never get to see Him if you don't struggle to get them right. -- Stephen Jay Gould ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
Re: [Monotone-devel] Initially creating a branch without committing changes?
In message <[EMAIL PROTECTED]> on Mon, 10 Sep 2007 20:56:53 +0200, Ludovic Brenta <[EMAIL PROTECTED]> said: ludovic> Thomas Keller <[EMAIL PROTECTED]> writes: ludovic> ludovic> > Ralf S. Engelschall schrieb: ludovic> >> The only possibility I've found is to manually issue an additional cert ludovic> >> for the new branch via: ludovic> >> ludovic> >> $ mtn cert h:foo.bar.cvs branch foo.bar ludovic> >> ludovic> >> This worked just fine. But I'm not sure whether whether this really is ludovic> >> the correct approach. ludovic> > ludovic> > This is the only way of doing this now. ludovic> ludovic> In the sense that "mtn approve h:foo.bar.cvs --branch foo.bar" does ludovic> the same thing, that is :) Or am I mistaken? Think twice before you do that, it could be a bit surprising (I know, I did it on the nvm branch ;-)). Cheers, Richard - Please consider sponsoring my work on free software. See http://www.free.lp.se/sponsoring.html for details. -- Richard Levitte [EMAIL PROTECTED] http://richard.levitte.org/ "When I became a man I put away childish things, including the fear of childishness and the desire to be very grown up." -- C.S. Lewis ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
Re: [Monotone-devel] Initially creating a branch without committing changes?
Thomas Keller <[EMAIL PROTECTED]> writes: > Ralf S. Engelschall schrieb: >> The only possibility I've found is to manually issue an additional cert >> for the new branch via: >> >> $ mtn cert h:foo.bar.cvs branch foo.bar >> >> This worked just fine. But I'm not sure whether whether this really is >> the correct approach. > > This is the only way of doing this now. In the sense that "mtn approve h:foo.bar.cvs --branch foo.bar" does the same thing, that is :) Or am I mistaken? > I've filed a bug [0] some time ago for pretty much the same > thing. Its an UI bug, which should just be fixed. > > Thomas. > > [0] http://savannah.nongnu.org/bugs/?func=detailitem&item_id=18201 -- Ludovic Brenta. ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] daemon support
Hi All, I just synced a branch called nvm.daemon-support. All tests are passing on my tree, but I've only got Ubuntu Feisty to test on right now. I hope that someone can build/test it on more platforms (windows would be especially helpful). Let me know if you can help out. Thanks -Ben -- --- Ben Walton <[EMAIL PROTECTED]> When one person suffers from a delusion, it is called insanity. When many people suffer from a delusion it is called Religion. Robert M. Pirsig, Zen and the Art of Motorcycle Maintenance --- ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
Re: [Monotone-devel] Initially creating a branch without committing changes?
Ralf S. Engelschall schrieb: > $ mtn cert h:foo.bar.cvs branch foo.bar > > This worked just fine. But I'm not sure whether whether this really is > the correct approach. > This is the correct approach. Propagating into empty branches would lead to lots of typo-branches (net.vnege.monotone.foo and the like), but adding --force to propagate might work, too. As for empty changes, I'm not sure if they are a good idea (and the UI prevents them, as you noticed). With enough sophistication, you could easily add them, if you really need them (put_revision - it happily accepts empty changesets, though that should probably be prevented) Regards, Patrick Georgi ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
Re: [Monotone-devel] Initially creating a branch without committing changes?
Ralf S. Engelschall schrieb: > The only possibility I've found is to manually issue an additional cert > for the new branch via: > > $ mtn cert h:foo.bar.cvs branch foo.bar > > This worked just fine. But I'm not sure whether whether this really is > the correct approach. This is the only way of doing this now. I've filed a bug [0] some time ago for pretty much the same thing. Its an UI bug, which should just be fixed. Thomas. [0] http://savannah.nongnu.org/bugs/?func=detailitem&item_id=18201 -- only dead fish swim with the stream: http://thomaskeller.biz/blog Am Anfang war das Wort: http://www.schäuble-muss-weg.de ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Initially creating a branch without committing changes?
Suppose I've imported (via Tailor) a CVS repository's module trunk into a Monotone repository and there onto branch "foo.bar.cvs". I then would like to have "foo.bar" the main development branch for the project and hence I want to initially create this "foo.bar" branch by just propagating the head revision of "foo.bar.cvs" into "foo.bar" -- BUT WITHOUT BEING REQUIRED TO MAKE ANY CHANGES BEFOREHAND. I just want that the initial revision on "foo.bar" is _IDENTICAL_ to the last revision (on the then effectively dead as long as one doesn't import more from CVS) "foo.bar.cvs" branch. It is clear to me that with... $ mtn --db=/path/to/mtn.db co -b foo.bar.cvs src $ cd src $ [MAKE SOME CHANGES] $ mtn ci -b foo.bar -m "create foo.bar branch" ...I can easily create the "foo.bar" branch. But this requires me to make some changes beforehand. Hmmm... I would have expected that I can do: $ mtn --db=/path/to/mtn.db propagate foo.bar.cvs foo.bar But this is denied because the "foo.bar" branch is still empty (or not existing). And there is also not something like a "--force" option to "mtn ci" or "mtn propagate" to let me DWIM. I assume the problem is that all this boils down to the issue of an "empty changeset" which seems to be something which (by design?) might to be not supported in Monotone, right? The only possibility I've found is to manually issue an additional cert for the new branch via: $ mtn cert h:foo.bar.cvs branch foo.bar This worked just fine. But I'm not sure whether whether this really is the correct approach. So, the main question for me is: what is best/correct approach to start a branch "foo.bar" and have its initial revision _identical_ to the latest revision on "foo.bar.cvs"? Ralf S. Engelschall [EMAIL PROTECTED] www.engelschall.com ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] monotone Hacking
Hi all! I've noticed that the changelog some people use for monotone is not quite "GNU-style". I'm sure you all hacked stuff longer than me, so you can correct me at any time, but aren't we forced to use some kind of GNU-style syntax to make it easier to create a ChangeLog file afterwards (for whatever distributions need that)? If not, everybody is - of course - free to use whatever format they do like. I don't like to start a bikeshed discussion here, I just want to be clear. I think it would also be a good idea to include the rules of whatever consense we find here in HACKING. Thomas. -- only dead fish swim with the stream: http://thomaskeller.biz/blog Am Anfang war das Wort: http://www.schäuble-muss-weg.de ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
