Re: [fossil-users] option "--abs-path" on fossil extras/changes doesn't work
I erroneously interpreted the CLI-help ("Display absolute pathnames") as:
"show the complete path of the changed file as recorded by the Filesystem".
Thanks!
Martin Gagnon schrieb am Sa, 8.3.2014:
Betreff: Re: [fossil-users] option "--abs-path" on fossil extras/changes
doesn't work
An: entspamt-fos...@yahoo.de, "Fossil SCM user's discussion"
Datum: Samstag, 8. März, 2014 21:18 Uhr
On Sat, Mar 08, 2014 at 07:47:04PM
+, entspamt-fos...@yahoo.de
wrote:
> Hi,
>
> d:\test>fossil settings relative-paths
> relative-paths (local) 1
>
> d:\test>fossil extras
> test1.txt
> test2.txt
>
> d:\test>fossil extras --abs-paths
> test1.txt
> test2.txt
>
> d:\test>fossil settings relative-paths 0
>
> d:\test>fossil settings relative-path
> relative-paths (local) 0
>
> d:\test>fossil extras
> test1.txt
> test2.txt
>
> d:\test>fossil extras --abs-paths
> test1.txt
> test2.txt
>
> This is on Windows 8.1 x64
Absolute path mean, absolute from the root of the checkout.
Since you
always execute your command from the root of the checkout,
relative or
absolute is equivalent. To see a difference you should try
to work from
a subdirectory inside the checkout.
d:\test>cd somedir
d:\test\somedir>fossil extra --abs-paths
test1.txt
test2.txt
d:\test\somedir>fossil extra --rel-paths
..\test1.txt
..\test2.txt
--
Martin G.
___
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] importing/forking from Git
Should I take it at this point that --incremental is deprecated and should not be used or expected to be present in future Fossil versions? So far, I have seen no responses that specifically addressed whether the behavior I expected from it was the intended behavior, whether anyone else might have the same problem indicating a bug in the software or whether this was confined to my situation and thus might be a local configuration issue, whether there was anything I could do to provide more information to help, and so on. The closest thing to meaningfully addressing the issue that I have seen was akin to the old joke . . . patient: Doctor, doctor, it hurts when I do this! doctor: Don't do that. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] ___ 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] option "--abs-path" on fossil extras/changes doesn't work
On Sat, Mar 08, 2014 at 07:47:04PM +, entspamt-fos...@yahoo.de wrote: > Hi, > > d:\test>fossil settings relative-paths > relative-paths (local) 1 > > d:\test>fossil extras > test1.txt > test2.txt > > d:\test>fossil extras --abs-paths > test1.txt > test2.txt > > d:\test>fossil settings relative-paths 0 > > d:\test>fossil settings relative-path > relative-paths (local) 0 > > d:\test>fossil extras > test1.txt > test2.txt > > d:\test>fossil extras --abs-paths > test1.txt > test2.txt > > This is on Windows 8.1 x64 Absolute path mean, absolute from the root of the checkout. Since you always execute your command from the root of the checkout, relative or absolute is equivalent. To see a difference you should try to work from a subdirectory inside the checkout. d:\test>cd somedir d:\test\somedir>fossil extra --abs-paths test1.txt test2.txt d:\test\somedir>fossil extra --rel-paths ..\test1.txt ..\test2.txt -- Martin G. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] option "--abs-path" on fossil extras/changes doesn't work
Hi, d:\test>fossil settings relative-paths relative-paths (local) 1 d:\test>fossil extras test1.txt test2.txt d:\test>fossil extras --abs-paths test1.txt test2.txt d:\test>fossil settings relative-paths 0 d:\test>fossil settings relative-path relative-paths (local) 0 d:\test>fossil extras test1.txt test2.txt d:\test>fossil extras --abs-paths test1.txt test2.txt This is on Windows 8.1 x64 Regards Oliver ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] stashing of added files
Hi, I'm new to fossil and not quite shure if this is a bug or a lack of understanding on my part. I wanted to stash a newly added file, then apply the stash to another (feature-)branch. Fossil worked as I had expected. At least it said so... c:\workspace>ver Microsoft Windows [Version 6.3.9600] c:\workspace>fossil init test.fossil project-id: 7805e88c40ce591187ce9bf5171ddbe8a0ec3357 server-id: 769e90784fb4622f5007a26e39ee4d9608228021 admin-user: admin (initial password is "4e4822") c:\workspace>fossil open test.fossil project-name: repository: c:/workspace/test.fossil local-root: c:/workspace/ config-db:C:/Users/admin/AppData/Local/_fossil project-code: 7805e88c40ce591187ce9bf5171ddbe8a0ec3357 checkout: be310e315ee733cfa10d1038fec7a5f89130b2cc 2014-03-08 17:40:47 UTC tags: trunk comment: initial empty check-in (user: admin) checkins: 1 c:\workspace>dir Directory of c:\workspace 08.03.2014 18:41 . 08.03.2014 18:41 .. 08.03.2014 18:4158.368 test.fossil 08.03.2014 18:41 7.168 _FOSSIL_ 2 File(s) 65.536 bytes 2 Dir(s) 8.336.400.384 bytes free c:\workspace>echo line1>main c:\workspace>fossil add main ADDED main c:\workspace>fossil ci -m main New_Version: aa095194ec545530135d9f3eeac27065ac7e6ecd c:\workspace>echo line1>newfeature c:\workspace>fossil add newfeature ADDED newfeature c:\workspace>fossil ci --branch branch1 -m newfeature New_Version: 63049c3042e725482950c0cbe529a8943a104c54 c:\workspace>fossil branch * branch1 trunk c:\workspace>fossil up trunk REMOVE newfeature --- updated-to: aa095194ec545530135d9f3eeac27065ac7e6ecd 2014-03-08 17:42:06 UTC tags: trunk comment: main (user: admin) changes: 1 file modified. "fossil undo" is available to undo changes to the working checkout. c:\workspace>echo line1>test c:\workspace>echo line2>>main c:\workspace>fossil add test ADDED test c:\workspace>fossil extra c:\workspace>fossil changes EDITED main ADDED test c:\workspace>fossil stash C:\Windows\notepad.exe "./ci-comment-655133848A97.txt" REVERTED: main UNMANAGE: test c:\workspace>fossil extra test c:\workspace>fossil update branch1 ADD newfeature --- updated-to: 63049c3042e725482950c0cbe529a8943a104c54 2014-03-08 17:43:22 UTC tags: branch1 comment: ADDED newfeature (user: admin) changes: 1 file modified. "fossil undo" is available to undo changes to the working checkout. c:\workspace>fossil stash diff CHANGED main --- main +++ main @@ -1,1 +1,2 @@ line1 +line2 ADDED test Index: test == --- test +++ test @@ -0,0 +1,1 @@ +line1 c:\workspace>fossil stash apply UPDATE main ADD test "fossil undo" is available to undo changes to the working checkout. c:\workspace>fossil extra test c:\workspace>fossil changes EDITED main c:\workspace>type main line1 line2 c:\workspace>type test line1 c:\workspace>fossil stash goto REMOVE newfeature --- updated-to: aa095194ec545530135d9f3eeac27065ac7e6ecd 2014-03-08 17:42:06 UTC tags: trunk comment: main (user: admin) changes: 1 file modified. MERGE main ADD test "fossil undo" is available to undo changes to the working checkout. c:\workspace>fossil branch branch1 * trunk c:\workspace>dir Directory of c:\workspace 08.03.2014 19:04 . 08.03.2014 19:04 .. 08.03.2014 19:0414 main 08.03.2014 19:04 7 test 08.03.2014 18:4358.368 test.fossil 08.03.2014 19:0417.408 _FOSSIL_ 4 File(s) 75.797 bytes 2 Dir(s) 7.889.629.184 bytes free c:\workspace>fossil changes EDITED main c:\workspace>fossil extra test Fossil did record the addition of file "test" to the stash, it even said it applied it on both occasions (stash apply, stash goto). So why did the file remain "unmanaged"? Regards Oliver ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
