What about nested checkouts? Which repo should it check to? I presume the first
_FOSSIL_ it finds.
What if you make a typo that results in the path which is a valid changed file
in unintended checkout? That would result in committing to wrong repo.
This could easily (certainly to me, at least) happen in case of multiple
checkouts from the same repo (e.g. feature or maintenance branches).
But to be fair, I'd rarely - if ever - commit from another directory. I always
cd to 'correct' one, do a stat/gdiff beforehand, etc.
Original Message
From: Warren Young
Sent: Wednesday, 13 May 2015 05:39
To: Fossil SCM user's discussion
Reply To: Fossil SCM user's discussion
Subject: [fossil-users] Allow checkins on another repo
“fossil ci” currently allows you to specify file or directory names, which
causes it to restrict the checkin to the named entities.
This is very useful within a single repository, but it breaks down when you try
to use it with multiple repo checkouts. Fossil doesn’t take those names into
account when locating the .fslckout file; it appears to only use CWD.
This causes extra work when you are working on two different repositories at
once, cd’d into one but changing files in the other. If you say something like:
$ fossil ci ~/some/other/repo/file.c
…then fossil will complain that file.c is not part of the current repo. It
makes you cd over to ~/some/other/repo just to check that file in, then cd
back. Fossil should be smart enough to realize that file.c belongs to a
*different* repo and DTRT.
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
