Re: [fossil-users] Unversioned files not accessible from Webinterface

[Richard Hipp]

On 2/22/17, Tony Papadimitriou  wrote:
> Unless the repo visitor happens
> to magically know about this /uvlist link there seems to be no obvious way
> to get to it starting navigation from some main page.

That is by design.  The intent is that the repository designer will
create a link to the /uvlist page on the homepage or on the menu or
some other appropriate place, if she intends for the /uvlist page to
be used.

On the Fossil self-hosting repository, the Download menu item is  a
link to a specific file in the /uv hierarchy that contains a formatted
list of unversioned files.  Knowledgeable users are free to visit
https://www.fossil-scm.org/fossil/uvlist if they like, but that is not
a page that we especially want to call to the attention of newbies.
-- 
D. Richard Hipp
d...@sqlite.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] Unversioned files not accessible from Webinterface

[Tony Papadimitriou]

Thank you for the tip, good to know.
(However, I think my point is still valid.  Unless the repo visitor happens to 
magically know about this /uvlist link there seems to be no obvious way to get 
to it starting navigation from some main page.)
From: Martin Gagnon 

To see the list of unversioned files on a repo, use the /uvlist page: 
example: https://www.fossil-scm.org/index.html/uvlist
___
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] Unversioned files not accessible from Web interface

[Martin Gagnon]

 Sorry my bad,  I was confused because on the main page the footer of the
page shows 1.34,   but I just notice that when going inside one repository
it's 1.36.

-- 
Martin G.

Le mer. 22 févr. 2017 à 11:45, Roy Keene  a écrit :

> ChiselApp runs Fossil 1.36 currently, not 1.34.
>
> On Wed, 22 Feb 2017, Martin Gagnon wrote:
>
> >
> > Le mer. 22 févr. 2017 à 03:33, Tony Papadimitriou  a
> écrit :
> >   I placed some unversioned file to a chiselapp repo I maintain and
> then from the Web UI tried to locate the file but without luck.
> > There isn?t even a hint that some unversioned file is in the repo, so
> that one can try to UNV SYNC from the command line (after cloning).
> >
> > Maybe the FILES tab should have an additional option (next to All,
> Tree-View, etc.) for Unversioned?  And from there process them (e.g.,
> download, hex) exactly the same.
> >
> >
> >
> > Hi Tony,
> >
> > To see the list of unversionned files on a repo, use the /uvlist page:
> >
> >  example: https://www.fossil-scm.org/index.html/uvlist
> >
> > But in your case, I'm afraid that Chiselapp use a too old version of
> fossil (1.34). unversionned files feature appear in 1.36.
> >
> > May be "unver sync" command could return an error in that case?
> >
> > Regards,
> >
> > --
> > 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 mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Unversioned files not accessible from Web interface

[Roy Keene]

ChiselApp runs Fossil 1.36 currently, not 1.34.

On Wed, 22 Feb 2017, Martin Gagnon wrote:



Le mer. 22 févr. 2017 à 03:33, Tony Papadimitriou  a écrit :
  I placed some unversioned file to a chiselapp repo I maintain and then 
from the Web UI tried to locate the file but without luck.
There isn?t even a hint that some unversioned file is in the repo, so that one 
can try to UNV SYNC from the command line (after cloning).
 
Maybe the FILES tab should have an additional option (next to All, Tree-View, 
etc.) for Unversioned?  And from there process them (e.g., download, hex) 
exactly the same.
 


Hi Tony, 

To see the list of unversionned files on a repo, use the /uvlist page: 

 example: https://www.fossil-scm.org/index.html/uvlist

But in your case, I'm afraid that Chiselapp use a too old version of fossil 
(1.34). unversionned files feature appear in 1.36.

May be "unver sync" command could return an error in that case? 

Regards,

-- 
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] tracking changes relatively to root directory on Unix

[Warren Young]

On Feb 21, 2017, at 7:07 PM, Petr Ferdus  wrote:
> 
> Would anyone suggest possible workaround for Unix with no way to open 
> repository placed in root of filesystem?

Who says you have to use just one repository for all of the directories you 
manage on the whole system?  Why not have one Fossil repo for each subtree?  
That not only gets around the problem you’re having, it probably makes more 
sense anyway.

For example, I have ~/.vim under Fossil’s management, but it’s opened as 
/home/mylogin/.vim on the Linux boxes, and /Users/mylogin/.vim on my macOS box. 
 If I’d checked that directory into a repo whose root is the same as the 
filesystem root, I’d have a Linux-specific or macOS-specific repo.

This doesn’t solve the problem for your read-only directories, but I’m a bit 
puzzled why you’d want those to be managed by Fossil anyway.  The core premise 
of Fossil is that you’re tracking the change history of files, which implies 
that you can *change* them.

If some other user can modify those files, *that* user should own the Fossil 
repository for those files.

___
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] Unversioned files not accessible from Web interface

[Martin Gagnon]

Le mer. 22 févr. 2017 à 03:33, Tony Papadimitriou  a écrit :

> I placed some unversioned file to a chiselapp repo I maintain and then
> from the Web UI tried to locate the file but without luck.
> There isn’t even a hint that some unversioned file is in the repo, so that
> one can try to UNV SYNC from the command line (after cloning).
>
> Maybe the FILES tab should have an additional option (next to All,
> Tree-View, etc.) for Unversioned?  And from there process them (e.g.,
> download, hex) exactly the same.
>
>

Hi Tony,

To see the list of unversionned files on a repo, use the /uvlist page:

 example: https://www.fossil-scm.org/index.html/uvlist

But in your case, I'm afraid that Chiselapp use a too old version of fossil
(1.34). unversionned files feature appear in 1.36.

May be "unver sync" command could return an error in that case?

Regards,

-- 
Martin G.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users