Hello Jean, On Sunday 18 September 2005 21:26, Jean Delvare wrote: > Hi all, > > I am proud to let you know about Quian, my web-based, read-only > front-end to quilt. You can see what it looks like here: > > http://jdelvare.net2.nerim.net/quian/2.6/
Quian relly looks nice! I'm eager to learn how much cpu and I/O bandwidth Quian consumes, and how fast it feels locally ;) I would have used Mercurial to produce a similar result, but Quian can present some things better than Mercurial. One thing we might want to add to quilt annotate is a view that displays the patch names side by side with the source code as Quian does. I so far didn't bother doing that because the code for figuring out how to properly align things scared me off. (Still shouldn't be more than a few lines of shell code...) Another would be to somehow get annotate to print which modifications are "underneath" the most recent modification, in case that's useful. Deletions might be interesting as well. > 1* File moves are not handled. As moving files around happens > frequently in the lifetime of a large project, some history is not > visible using Quian. I have plans to improve quilt's annotate command, > but it sounds like a quite complex task, as patch files do not clearly > notify file moves. You won't get that information with patch based tools, and I don't think it makes a lot of sense trying to reconstruct this information. Any of the modern version control tools can do this though. > 2* I had to modify quilt's diff command not do print warnings on > stderr, else my Apache's logs were full of these. This explains a > recent post of mine [1] to this list. I hope to come up with a solution > that will make everyone happy before I can release Quian's code to the > public. I want people to be able to use Quian with a stock quilt > installation. Isn't I/O redirection good enough? Cheers, Andreas. _______________________________________________ Quilt-dev mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/quilt-dev
