Re: [fossil-users] changes & status cmds within sub-directory
Le 2011-07-10 à 11:05, Ben Summers a écrit : > Answering the question about breaking existing scripts, the output is > identical when used at the root. Unless you're running scripts in a > sub-directory, nothing needs to change. > > Ben > That's true... And I like the latest suggestion as well... But I still would like to have the possibility to do a timeline restricted to a subdir. Like the way we can show a timeline for commits done by a specific user ... -- Martin ___ 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] changes & status cmds within sub-directory
On Sun, Jul 10, 2011 at 10:12:33AM -0400, Joshua Paine wrote: > On 7/10/2011 9:11 AM, Ben Summers wrote: > > $ fossil status > > In sub-directory two: > > ADDED world.txt > > EDITED src/display.c > > 1 other change. Use --show-all option to list all changes. > > I would rather it work like git and show other changes as well, but > relative to the current location. E.g., > > ADDED ../one/hello.txt > ADDED world.txt > EDITED src/display.c Yes, that's much nicer to use, and to implement. Try it here: http://fossil-scm.org/index.html/info/a05bbff46a Use the --non-relative option to get the current output. Answering the question about breaking existing scripts, the output is identical when used at the root. Unless you're running scripts in a sub-directory, nothing needs to change. Ben -- http://bens.me.uk/ ___ 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] changes & status cmds within sub-directory
On Sun, Jul 10, 2011 at 10:12:33AM -0400, Joshua Paine wrote: > On 7/10/2011 9:11 AM, Ben Summers wrote: > > $ fossil status > > In sub-directory two: > > ADDED world.txt > > EDITED src/display.c > > 1 other change. Use --show-all option to list all changes. > > I would rather it work like git and show other changes as well, but > relative to the current location. E.g., > > ADDED ../one/hello.txt > ADDED world.txt > EDITED src/display.c I prefer this, over all presented in the thread until now. ___ 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] changes & status cmds within sub-directory
On 7/10/2011 9:11 AM, Ben Summers wrote: > $ fossil status > In sub-directory two: > ADDED world.txt > EDITED src/display.c > 1 other change. Use --show-all option to list all changes. I would rather it work like git and show other changes as well, but relative to the current location. E.g., ADDED ../one/hello.txt ADDED world.txt EDITED src/display.c In SVN it makes sense to have commands act on specific directories only, since any directory can be checked out by itself. With an all-or-nothing approach as is common in the DVCSes, I think adjusting the output so that the paths are useful wherever you are now is helpful, but hiding some changes is a mistake. -- 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
Re: [fossil-users] changes & status cmds within sub-directory
Le 2011-07-10 à 09:11, Ben Summers a écrit : > > When working on my project, the current directory is always a sub-directory > of the checkout root. Perhaps I'm too used to subversion, but I'm finding the > checkout root-relative listing rather confusing. You can't copy and paste a > filename to, say, an add command without having to think about removing the > sub-directory name. > > I wonder if modifying the output when you're in a sub-directory would be a > good idea to help the people who work like this. (Although I suspect that the > vast majority of people work in the root directory.) > > If the current directory was the 'two' sub-directory, currently the output > might look like this: > > $ fossil status > ADDED one/hello.txt > ADDED two/world.txt > EDITED two/src/display.c > > I'd find it easier to work with if it were displayed like this: > > $ fossil status > In sub-directory two: > ADDED world.txt > EDITED src/display.c > 1 other change. Use --show-all option to list all changes. > > I've implemented this in a branch: > http://fossil-scm.org/index.html/info/e0d2e1f9b8 > > If you happen to be in the root directory, or use the --show-all option, the > output is identical to the current version. > > Does this sound like a good idea? > > I would rather add the capability to do: # fossil status two From the root which will give the listing of only what is in two. This will not change default behavior of fossil when called without argument Or from inside the dir you can do: # fossil status . Or add switch which does the opposite of the --show-all switch you implement. I guess changing default behavior will break a lot of GUI wrapper or any program that parse the output of fossil. This is not the case with the way I propose. Also, a lot of other command might be useful on subdirectories, like timeline, change etc... -- Martin ___ 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] changes & status cmds within sub-directory
Hmm, maybe just --all/-a? "show --show-all" seems a bit redundant. Otherwise, I won't bikeshed, and that does seem like a good idea. On 07/10/2011 08:11 AM, Ben Summers wrote: > When working on my project, the current directory is always a sub-directory > of the checkout root. Perhaps I'm too used to subversion, but I'm finding the > checkout root-relative listing rather confusing. You can't copy and paste a > filename to, say, an add command without having to think about removing the > sub-directory name. > > I wonder if modifying the output when you're in a sub-directory would be a > good idea to help the people who work like this. (Although I suspect that the > vast majority of people work in the root directory.) > > If the current directory was the 'two' sub-directory, currently the output > might look like this: > > $ fossil status > ADDED one/hello.txt > ADDED two/world.txt > EDITED two/src/display.c > > I'd find it easier to work with if it were displayed like this: > > $ fossil status > In sub-directory two: > ADDED world.txt > EDITED src/display.c > 1 other change. Use --show-all option to list all changes. > > I've implemented this in a branch: > http://fossil-scm.org/index.html/info/e0d2e1f9b8 > > If you happen to be in the root directory, or use the --show-all option, the > output is identical to the current version. > > Does this sound like a good idea? > > Ben > > > > -- > http://bens.me.uk/ > > > > ___ > 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] changes & status cmds within sub-directory
On Sun, Jul 10, 2011 at 3:11 PM, Ben Summers wrote: > I've implemented this in a branch: > http://fossil-scm.org/index.html/info/e0d2e1f9b8 > > Does this sound like a good idea? > amen! -- - 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
[fossil-users] changes & status cmds within sub-directory
When working on my project, the current directory is always a sub-directory of the checkout root. Perhaps I'm too used to subversion, but I'm finding the checkout root-relative listing rather confusing. You can't copy and paste a filename to, say, an add command without having to think about removing the sub-directory name. I wonder if modifying the output when you're in a sub-directory would be a good idea to help the people who work like this. (Although I suspect that the vast majority of people work in the root directory.) If the current directory was the 'two' sub-directory, currently the output might look like this: $ fossil status ADDED one/hello.txt ADDED two/world.txt EDITED two/src/display.c I'd find it easier to work with if it were displayed like this: $ fossil status In sub-directory two: ADDED world.txt EDITED src/display.c 1 other change. Use --show-all option to list all changes. I've implemented this in a branch: http://fossil-scm.org/index.html/info/e0d2e1f9b8 If you happen to be in the root directory, or use the --show-all option, the output is identical to the current version. Does this sound like a good idea? Ben -- http://bens.me.uk/ ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
