Re: [fossil-users] Developing on Unix and Windows
Am Samstag 24 Oktober 2009 schrieb Dmitry Chestnykh: > Hi, > > Instead of making Fossil call filters, why not create scripts that > call Fossil? > > my_commit: > > #!/bin/sh > run_filter > fossil commit %@ > > my_checkout: > > #!/bin/sh > fossil checkout %@ > run_filter > Yes, that also would be a solution. Ruediger ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Committing a subdirectory
On Sat, Oct 24, 2009 at 5:16 PM, D. Richard Hipp wrote: > There is no command to commit a subdirectory. You can commit > individual files by naming them on the commit command-line, but there > is no shorthand for specifying all the files in a subdirectory. > Hi, Richard! Is it correct to say that fossil doesn't really know what directories are? i.e. that two artifacts might be named: foo/f1 foo/f2 and fossil doesn't "know" that they're in the same directory? (And doesn't really care that they happen to have the same filename prefix?) :-? (Just curious.) -- - stephan beal http://wanderinghorse.net/home/stephan/ ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Committing a subdirectory
On Oct 24, 2009, at 10:57 AM, Nick B wrote: > I have a number of modified files but I would like to commit only a > few files in a single subdirectory. > > Typing "fossil changes" returns > > MISSING brightside/images/bg.gif > EDITED brightside/images/headerbg.gif > EDITED brightside/images/tableft.gif > EDITED brightside/images/tabright.gif > > In the parent directory if I enter: > "fossil commit images" or "fossil commit images/" returns > "fossil: fossil knows nothing about: images/" > > Similarly if I use: > > "fossil commit images/*" returns > "fossil: fossil knows nothing about: images/bg.gif.old" > > In this case the file bg.gif.old can be safely ignored as I only want > to commit edited files. > > What command do I use to commit the subdirectory images? There is no command to commit a subdirectory. You can commit individual files by naming them on the commit command-line, but there is no shorthand for specifying all the files in a subdirectory. In your case, it might work to do: fossil commit images/*.gif since the .gif suffix will omit the .old file. But there is no general solution at this time. You are welcomed to contribute one :-) > > Thanks > ___ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users D. Richard Hipp d...@hwaci.com ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Committing a subdirectory
On Sat, Oct 24, 2009 at 02:57:11PM +, Nick B wrote: > I have a number of modified files but I would like to commit only a > few files in a single subdirectory. > > Typing "fossil changes" returns > > MISSING brightside/images/bg.gif > EDITED brightside/images/headerbg.gif > EDITED brightside/images/tableft.gif > EDITED brightside/images/tabright.gif > > In the parent directory if I enter: > "fossil commit images" or "fossil commit images/" returns > "fossil: fossil knows nothing about: images/" > > Similarly if I use: > > "fossil commit images/*" returns > "fossil: fossil knows nothing about: images/bg.gif.old" > > In this case the file bg.gif.old can be safely ignored as I only want > to commit edited files. > > What command do I use to commit the subdirectory images? > > Thanks _ When I add a subdirectory to my repository I usually do fossil add subdirectory which will add the subdirectory and its contents. Future 'fossil commit' automatically get the editted files in the subdirectory. You would have to 'fossil add' any new ones. If you already have cruft in the subdir, though, and have not added the subdir, then doing fossil add subdirectory will add all the cruft as well. I suppose that at this point I would manually clean out (i.e. mv to a tmp location) anything I did not want to 'fossil add' which is in the images subdirectory, do the 'fossil add images', and then move whatever I wanted back into the directory. ~Michael ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Committing a subdirectory
I have a number of modified files but I would like to commit only a few files in a single subdirectory. Typing "fossil changes" returns MISSING brightside/images/bg.gif EDITED brightside/images/headerbg.gif EDITED brightside/images/tableft.gif EDITED brightside/images/tabright.gif In the parent directory if I enter: "fossil commit images" or "fossil commit images/" returns "fossil: fossil knows nothing about: images/" Similarly if I use: "fossil commit images/*" returns "fossil: fossil knows nothing about: images/bg.gif.old" In this case the file bg.gif.old can be safely ignored as I only want to commit edited files. What command do I use to commit the subdirectory images? Thanks ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Developing on Unix and Windows
Hi, Instead of making Fossil call filters, why not create scripts that call Fossil? my_commit: #!/bin/sh run_filter fossil commit %@ my_checkout: #!/bin/sh fossil checkout %@ run_filter -- Dmitry Chestnykh Coding Robots http://www.codingrobots.com dmi...@codingrobots.com On 24.10.2009, at 15:47, Rüdiger Härtel wrote: > Hello, > > I want to throw in my 2 cents, too. > > I don't see why fossil shouldn't provide any facility to run files > through a > filter or preprocessor before checkin, after check out and maybe > there are > other actions when running a file through a filter is useful or > necessary. > > When a developer uses this filter for converting line endings, let > her do so. > Maybe someone wants to indent source files before checkin. > There are many cases where it makes sense to the developer. > > Ruediger ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Developing on Unix and Windows
Hello, I want to throw in my 2 cents, too. I don't see why fossil shouldn't provide any facility to run files through a filter or preprocessor before checkin, after check out and maybe there are other actions when running a file through a filter is useful or necessary. When a developer uses this filter for converting line endings, let her do so. Maybe someone wants to indent source files before checkin. There are many cases where it makes sense to the developer. Ruediger Am Mittwoch 21 Oktober 2009 schrieb Ramon Ribó: > Hello, > > When developing the same program on Unix and on Windows, cvs > automatically converts the line > end of the files to the appropriates for every platform. In this way, > if we commit a file in windows that > contains "\r\n" as line ends, we can checkout this file on unix and it > will have "\n" line ends. > > As I see, fossil does not change the line endings of the ascii > files. If we try to work as is, I see several > problems, for example, scripts begin with "#!" on unix do not work if > they have "\r\n" as line end" > > What is the opinion of the fossil users & developers on this? What > is the suggested method for developing > the same program in both unix and windows? will fossil be modified in > the future to contain an automatic > translation of line endings? > ___ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Developing on Unix and Windows
Last time I used vi, it showed ^M at end of each line... does the new version classify files as DOS/Unix and handles edits correctly? - Altu -Original Message- From: Stephen De Gabrielle To: fossil-users@lists.fossil-scm.org Sent: Fri, Oct 23, 2009 1:44 pm Subject: Re: [fossil-users] Developing on Unix and Windows vi emacs s. On Fri, Oct 23, 2009 at 8:09 AM, wrote: > I'm not much familiar with editors in unix. Are there good editors in > unix that handle \r\n correctly? > > - Altu > > -Original Message- > From: Joshua Paine > To: fossil-users@lists.fossil-scm.org > Sent: __aolWsbDateToL10n__Wed, 21 Oct 2009 11:42:47 > -0400__aolWsbDateToL10n__ > Subject: Re: [fossil-users] Developing on Unix and Windows > > On Wed, 2009-10-21 at 17:09 +0200, Ramon Ribó wrote: >> 1- A TCL file is checked in on windows >> 2- It is checked out on unix and line ending is "\r\n" > > When the file is created on Windows, it should be created using unix > line endings. This is very easy to do in most editors. You can just set > it as your default and no one gets hurt. Everything except Notepad can > view it fine. > >> 1- I create a nice README or License file for my application in unix >> 3- README files are open by the user (not by my that I use a > wonderful >> convert-all editor). In Windows, they typically open with > Notepad. >> 4- The file is viewed as with one very long line > > Since your end users are not likely to checkout your code from fossil, I > don't think fossil's behavior is very relevant here. Either create your > README with windows line endings, or add some kind of conversion into > your build process when you produce packages for end users. > > For source code, my experience is that unix endings work everywhere for > running or viewing--except windows notepad. If there is any language > available on both windows and linux where a file will run/compile on > windows if it has windows endings *but not* if it has unix endings and > likewise will run on linux only with unix endings, then I have some > sympathy for your plight. Frankly, though, probably not enough that I > would want to see such an ugly feature built into fossil. > > -- > Joshua Paine > LetterBlock: Web applications built with joy > http://letterblock.com/ > 301-576-1920 > > ___ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > > > ___ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > -- -- Stephen De Gabrielle stephen.degabrie...@acm.org Telephone +44 (0)20 85670911 Mobile+44 (0)79 85189045 http://www.degabrielle.name/stephen ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
