[fossil-users] Valentine's Day wish
I recently discovered fossil and so far I like it very much. It does most of the things I need and does them very well. If I would be asked to name one feature that fossil still lacks I would name my favorite one: - Ability to push one branch at a time. Right now "fossil push" is all-or-nothing proposition -- all public branches are pushed, all private branches are ignored. Ability to push individual (public) branches would allow to easily facilitate many workflows that are now impossible or very cumbersome. I hope this feature can make it onto the TODO list and be eventually implemented. --Leo-- ___ 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] zip/tar patch
any interest in this simple patch?
hmm, on Tue, Feb 07, 2012 at 07:48:30PM +0100, frantisek holop said that
> hi there,
>
> the motivation for this patch was that the zip and tarball links
> from the web ui get a filename and checkout "for free", while they
> are a mandatory parameters for the command line.
>
> so i tried to unify it a bit: the default archive name is now both
> from web and cli the same, a lowercased project name followed by the
> artifact ID. spaces are substituted with '-'.
>
> $ fossil zip
> fossil-030035345c.zip: 2944427 bytes
>
> $ fossil zip tip
> fossil-030035345c.zip: 2944427 bytes
>
> $ fossil zip -o f.zip
> f.zip: 2944427 bytes
>
> $ fossil zip -o f.zip tip
> f.zip: 2944427 bytes
>
> $ fossil tar
> fossil-030035345c.tgz: 2944427 bytes
>
> $ fossil tar tip
> fossil-030035345c.tgz: 2944427 bytes
>
> $ fossil tar -o f.tgz
> f.zip: 2944427 bytes
>
> $ fossil tar -o f.tgz tip
> f.zip: 2944427 bytes
>
>
> $ fossil help zip
> Usage: fossil zip [--name DIRECTORY] [-o OUTPUTFILE]
> [-R REPOSITORY] [VERSION]
>
> Generate a ZIP archive containing VERSION of the checkout.
> If VERSION is omitted, the current checkout is used.
>
> The name of the resulting archive can be set using the -o option,
> otherwise it will be derived from the project name followed by the
> check-in's artifact ID. Unless the --name option is specified, the
> the top-level directory inside the archive will have the same name.
>
> Options:
> --name DIRECTORY Name of the top-level directory inside
> the archive.
> -o OUTPUTFILE Name of the archive.
> -R|--repository FILE Use the repository in FILE.
>
> See also: tarball
>
>
>
> --- src/info.c
> +++ src/info.c
> @@ -500,11 +500,18 @@
> @ %h(zUser) @ %h(zIpAddr) on %s(zDate)
>}
>db_finalize(&q);
> }
> if( g.perm.History ){
> - const char *zProjName = db_get("project-name", "unnamed");
> + char *zProjName = db_get("project-name", "unnamed");
> + int i;
> + for(i=0; i +zProjName[i] = fossil_tolower(zProjName[i]);
> +if( zProjName[i]==' ' ){
> + zProjName[i] = '-';
> + }
> + }
>@ Timelines:
>@ family
>if( zParent ){
> @ | ancestors
>}
> @@ -526,16 +533,14 @@
>@
>@ Other Links:
>@
>@ files
>if( g.perm.Zip ){
> -char *zUrl = mprintf("%s/tarball/%s-%S.tar.gz?uuid=%s",
> - g.zTop, zProjName, zUuid, zUuid);
> -@ | Tarball
> +@ | href="%s(g.zTop)/tarball/%s(zProjName)-%S(zUuid).tgz=%s(zUuid)">
> +@ Tarball
> @ | href="%s(g.zTop)/zip/%s(zProjName)-%S(zUuid).zip?uuid=%s(zUuid)">
> @ ZIP archive
> -fossil_free(zUrl);
>}
>@ | manifest
>if( g.perm.Write ){
> @ | edit
>}
>
> --- src/tar.c
> +++ src/tar.c
> @@ -525,42 +525,63 @@
> }
>
> /*
> ** COMMAND: tarball*
> **
> -** Usage: %fossil tarball VERSION OUTPUTFILE [--name DIRECTORYNAME]
> [-R|--repository REPO]
> +** Usage: %fossil tarball [--name DIRECTORY] [-o OUTPUTFILE]
> +** [-R REPOSITORY] VERSION
> +**
> +** Generate a compressed tarball archive containing VERSION of the
> +** project. If VERSION is omitted, the current checkout is used.
> +**
> +** The name of the resulting archive can be set using the -o option,
> +** otherwise it will be derived from the project name followed by the
> +** check-in's artifact ID. Unless the --name option is specified, the
> +** the top-level directory inside the archive will have the same name.
> +**
> +** Options:
> +** --name DIRECTORY Name of the top-level directory inside
> +** the archive.
> +** -o OUTPUTFILE Name of the archive.
> +** -R|--repository FILE Use the repository in FILE.
> **
> -** Generate a compressed tarball for a specified version. If the --name
> -** option is used, its argument becomes the name of the top-level directory
> -** in the resulting tarball. If --name is omitted, the top-level directory
> -** named is derived from the project name, the check-in date and time, and
> -** the artifact ID of the check-in.
> +** See also: zip
> */
> void tarball_cmd(void){
>int rid;
>Blob tarball;
>const char *zName;
> + const char *fName;
> + int wrote;
>zName = find_option("name", 0, 1);
> + fName = find_option("o", "o", 1);
>db_find_and_open_repository(0, 0);
> - if( g.argc!=4 ){
> -usage("VERSION OUTPUTFILE");
> + if( g.argc!=2 && g.argc!=3 ){
> +usage("[--name DIRECTORY] [-o OUTPUTFILE] [-R REPOSITORY] [VERSION]");
>}
> - rid = name_to_typed_rid(g.argv[2], "ci");
> + if( g.argc==3 ){
> +rid = name_to_typed_rid(g.argv[2], "ci");
> + }else{
> +rid = db_lget_int("checkout",0);
> + }
>if( zName==0 ){
> -zName = db_text("default-name",
> -
Re: [fossil-users] zip/tar patch
On Sat, Feb 11, 2012 at 7:55 AM, frantisek holop wrote:
>
> any interest in this simple patch?
>
I think the proposed behavior is a good way to go.
> hmm, on Tue, Feb 07, 2012 at 07:48:30PM +0100, frantisek holop said that
> > hi there,
> >
> > the motivation for this patch was that the zip and tarball links
> > from the web ui get a filename and checkout "for free", while they
> > are a mandatory parameters for the command line.
> >
> > so i tried to unify it a bit: the default archive name is now both
> > from web and cli the same, a lowercased project name followed by the
> > artifact ID. spaces are substituted with '-'.
> >
> > $ fossil zip
> > fossil-030035345c.zip: 2944427 bytes
> >
> > $ fossil zip tip
> > fossil-030035345c.zip: 2944427 bytes
> >
> > $ fossil zip -o f.zip
> > f.zip: 2944427 bytes
> >
> > $ fossil zip -o f.zip tip
> > f.zip: 2944427 bytes
> >
> > $ fossil tar
> > fossil-030035345c.tgz: 2944427 bytes
> >
> > $ fossil tar tip
> > fossil-030035345c.tgz: 2944427 bytes
> >
> > $ fossil tar -o f.tgz
> > f.zip: 2944427 bytes
> >
> > $ fossil tar -o f.tgz tip
> > f.zip: 2944427 bytes
> >
> >
> > $ fossil help zip
> > Usage: fossil zip [--name DIRECTORY] [-o OUTPUTFILE]
> > [-R REPOSITORY] [VERSION]
> >
> > Generate a ZIP archive containing VERSION of the checkout.
> > If VERSION is omitted, the current checkout is used.
> >
> > The name of the resulting archive can be set using the -o option,
> > otherwise it will be derived from the project name followed by the
> > check-in's artifact ID. Unless the --name option is specified, the
> > the top-level directory inside the archive will have the same name.
> >
> > Options:
> > --name DIRECTORY Name of the top-level directory inside
> > the archive.
> > -o OUTPUTFILE Name of the archive.
> > -R|--repository FILE Use the repository in FILE.
> >
> > See also: tarball
> >
> >
> >
> > --- src/info.c
> > +++ src/info.c
> > @@ -500,11 +500,18 @@
> > @ %h(zUser) @ %h(zIpAddr) on %s(zDate)
> >}
> >db_finalize(&q);
> > }
> > if( g.perm.History ){
> > - const char *zProjName = db_get("project-name", "unnamed");
> > + char *zProjName = db_get("project-name", "unnamed");
> > + int i;
> > + for(i=0; i > +zProjName[i] = fossil_tolower(zProjName[i]);
> > +if( zProjName[i]==' ' ){
> > + zProjName[i] = '-';
> > + }
> > + }
> >@ Timelines:
> >@ family
> >if( zParent ){
> > @ | ancestors
> >}
> > @@ -526,16 +533,14 @@
> >@
> >@ Other Links:
> >@
> >@ files
> >if( g.perm.Zip ){
> > -char *zUrl = mprintf("%s/tarball/%s-%S.tar.gz?uuid=%s",
> > - g.zTop, zProjName, zUuid, zUuid);
> > -@ | Tarball
> > +@ | href="%s(g.zTop)/tarball/%s(zProjName)-%S(zUuid).tgz=%s(zUuid)">
> > +@ Tarball
> > @ | href="%s(g.zTop)/zip/%s(zProjName)-%S(zUuid).zip?uuid=%s(zUuid)">
> > @ ZIP archive
> > -fossil_free(zUrl);
> >}
> >@ | manifest
> >if( g.perm.Write ){
> > @ | edit
> >}
> >
> > --- src/tar.c
> > +++ src/tar.c
> > @@ -525,42 +525,63 @@
> > }
> >
> > /*
> > ** COMMAND: tarball*
> > **
> > -** Usage: %fossil tarball VERSION OUTPUTFILE [--name DIRECTORYNAME]
> [-R|--repository REPO]
> > +** Usage: %fossil tarball [--name DIRECTORY] [-o OUTPUTFILE]
> > +** [-R REPOSITORY] VERSION
> > +**
> > +** Generate a compressed tarball archive containing VERSION of the
> > +** project. If VERSION is omitted, the current checkout is used.
> > +**
> > +** The name of the resulting archive can be set using the -o option,
> > +** otherwise it will be derived from the project name followed by the
> > +** check-in's artifact ID. Unless the --name option is specified, the
> > +** the top-level directory inside the archive will have the same name.
> > +**
> > +** Options:
> > +** --name DIRECTORY Name of the top-level directory inside
> > +** the archive.
> > +** -o OUTPUTFILE Name of the archive.
> > +** -R|--repository FILE Use the repository in FILE.
> > **
> > -** Generate a compressed tarball for a specified version. If the --name
> > -** option is used, its argument becomes the name of the top-level
> directory
> > -** in the resulting tarball. If --name is omitted, the top-level
> directory
> > -** named is derived from the project name, the check-in date and time,
> and
> > -** the artifact ID of the check-in.
> > +** See also: zip
> > */
> > void tarball_cmd(void){
> >int rid;
> >Blob tarball;
> >const char *zName;
> > + const char *fName;
> > + int wrote;
> >zName = find_option("name", 0, 1);
> > + fName = find_option("o", "o", 1);
> >db_find_and_open_repository(0, 0);
> > - if( g.argc!=4 ){
> > -usage("
Re: [fossil-users] zip/tar patch
On Sat, Feb 11, 2012 at 03:55:10PM +0100, frantisek holop wrote: > > any interest in this simple patch? In general I don't mind. But in particular: a) the patch has wrong indentation in some places b) I prefer .tar.gz over .tgz c) I like *both* uuid and date in the file names Regards, Lluís. > hmm, on Tue, Feb 07, 2012 at 07:48:30PM +0100, frantisek holop said that > > hi there, > > > > the motivation for this patch was that the zip and tarball links > > from the web ui get a filename and checkout "for free", while they > > are a mandatory parameters for the command line. > > > > so i tried to unify it a bit: the default archive name is now both > > from web and cli the same, a lowercased project name followed by the > > artifact ID. spaces are substituted with '-'. ___ 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] zip/tar patch
hmm, on Sat, Feb 11, 2012 at 05:27:41PM +0100, Lluís Batlle i Rossell said that > On Sat, Feb 11, 2012 at 03:55:10PM +0100, frantisek holop wrote: > > > > any interest in this simple patch? > > In general I don't mind. But in particular: > a) the patch has wrong indentation in some places could you be more speficic please? i tried to follow the main style but i admit its not my preferred indentation. > b) I prefer .tar.gz over .tgz > c) I like *both* uuid and date in the file names i guess these will be the final decision of the project leader.. unless using placeholders, there is no chance to please everyone. in my patch i followed what the web ui does as i thought that to be the preffered version. -f -- age is only skin deep. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] direct link to source and line number
Hello,
I have using ndoc to generate inline documentation for my project. It
has a feature to generate a direct link to a particular area of code.
Something like
$ ndoc -l http://web.hosting.fossil/\{file\}/#L\{line\} .
For example this will generate a link to
http://web.hosting.fossil/src/main.c#L98
My question is does fossil provide a direct link to a file and a line number?
I managed to find as a start,
I can use http://web.hosting.fossil/projectName/doc/trunk/\{file\} to
point to the latest, such as
http://web.hosting.fossil/myProject/doc/trunk/src/main.c
but it doesn't have the capability to go to line numbers and it
doesn't use the coded added to the header in the settings.
I would use the artifact page (which has some scripts to provide
syntax highlighting and named anchor for the line numbers), but that
uses the artifact ID.
Can anyone help?
Thanks Everyone!
--
"What Can't be explained with Logic is Magic"
"If it is not logic, it’s magic. If it is not magic, it is female logic."
"Lo que peude ser un hombre otro hombre tambien lo puede ser"
___
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] direct link to source and line number
Here is an example: http://www.fossil-scm.org/index.html/artifact?ci=tip&filename=src/main.c&ln= 57-80 -- Joe Mistachkin ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
