Re: [fossil-users] Adding Fossil to Windows Explorer context menu?
On Thu, 20 Oct 2011 15:56:43 +0200, Kohn Bernhard bernhard.k...@ait.ac.at wrote: http://imageshack.us/photo/my-images/830/fastexplorerfos.png I notice that none of the commands you added to the menu use parameters. I wanted to add gdiff --from previous %1, but I can't get Fast Explorer to send the full path to the file if it contains spaces :-/ ___ 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] Creating new branch/repository problems
On Thu, Oct 20, 2011 at 8:01 PM, Jared Harder jared.har...@gmail.comwrote: No matter what command I try, the error message is always the same: ./fossil: repository does not exist or is in an unreadable directory: /home/drh/sqlite/fossil.fossil Very curious. The /home/drh/sqlite/fossil.fossil pathname is the location of the Fossil repository for Fossil on a machine that I was using as my desktop up until about 2 months ago. So I thought perhaps I had used that name in an example script somewhere. But grep is not finding it. And that pathname is not found anywhere (that I can find) in the canonical Fossil repository on http://www.fossil-scm.org/. I'm very eager to learn how Jared got a checkout that thinks its repository is located at /home/drh/sqlite/fossil.fossil. Can you give us more information about where your repository came from, Jared? -- 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
[fossil-users] Fossil version 1.20 released
Fossil version 1.20 is now available for download at http://www.fossil-scm.org/download.html -- 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] Adding Fossil to Windows Explorer context menu?
On Fri, 21 Oct 2011 13:15:14 +0200, Gilles gilles.gana...@free.fr wrote: I wanted to add gdiff --from previous %1, but I can't get Fast Explorer to send the full path to the file if it contains spaces :-/ Problem solved: I thought FastExplorer sent all the parameters as a single string, while it sends each as an independent parameter, so that we must loop through them in the application that sits between Fast Explorer and fossil.exe. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] feature list?
Hello, A while back, drh posted a list of features which he couldn't implement due to time constraints, but I am unable to find that particular mail. Anyone have a link to the mail in the archives, or is that list available through the fossil wiki? -- Kind regards, Jan Danielsson ___ 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] feature list?
On Sat, 22 Oct 2011 01:55:31 +0200 Jan Danielsson jan.m.daniels...@gmail.com wrote: A while back, drh posted a list of features which he couldn't implement due to time constraints, but I am unable to find that particular mail. Anyone have a link to the mail in the archives, or is that list available through the fossil wiki? Here it is: http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg05846.html -- Dmitry Chestnykh http://www.codingrobots.com ___ 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] feature list?
On 10/22/11 02:00, Dmitry Chestnykh wrote: A while back, drh posted a list of features which he couldn't implement due to time constraints, but I am unable to find that particular mail. Anyone have a link to the mail in the archives, or is that list available through the fossil wiki? Here it is: http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg05846.html Thank you. Concerning point 2: -- (2) Add the ability to push/pull/sync just a specific branch, as an alternative to the current behavior of push/pull/sync of everything. The current behavior should continue as the default. Single-branch push/pull/sync should be a command-line option. -- Should this be interpreted literally: That only pull, push and sync would support specifying a subset of artifacts -- or should it be interpreted as including clone as well? -- Kind regards, Jan Danielsson ___ 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] feature list?
On Fri, Oct 21, 2011 at 9:35 PM, Jan Danielsson jan.m.daniels...@gmail.comwrote: On 10/22/11 02:00, Dmitry Chestnykh wrote: A while back, drh posted a list of features which he couldn't implement due to time constraints, but I am unable to find that particular mail. Anyone have a link to the mail in the archives, or is that list available through the fossil wiki? Here it is: http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg05846.html Thank you. Concerning point 2: -- (2) Add the ability to push/pull/sync just a specific branch, as an alternative to the current behavior of push/pull/sync of everything. The current behavior should continue as the default. Single-branch push/pull/sync should be a command-line option. -- Should this be interpreted literally: That only pull, push and sync would support specifying a subset of artifacts -- or should it be interpreted as including clone as well? Clone too. Also options to push/pull/sync/clone just wiki or tickets. -- Kind regards, Jan Danielsson ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- 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] Creating new branch/repository problems
On Fri, Oct 21, 2011 at 7:34 AM, Richard Hipp d...@sqlite.org wrote: On Thu, Oct 20, 2011 at 8:01 PM, Jared Harder jared.har...@gmail.comwrote: No matter what command I try, the error message is always the same: ./fossil: repository does not exist or is in an unreadable directory: /home/drh/sqlite/fossil.fossil Very curious. The /home/drh/sqlite/fossil.fossil pathname is the location of the Fossil repository for Fossil on a machine that I was using as my desktop up until about 2 months ago. So I thought perhaps I had used that name in an example script somewhere. But grep is not finding it. And that pathname is not found anywhere (that I can find) in the canonical Fossil repository on http://www.fossil-scm.org/. I'm very eager to learn how Jared got a checkout that thinks its repository is located at /home/drh/sqlite/fossil.fossil. Joe Mistachkin solved this mystery. The source tarballs from the download page were built incorrectly - they included the _FOSSIL_ file from my development folder. And that _FOSSIL_ file points to the repository on /home/drh/sqlite/fossil.fossil. Apparently, Jared built from the source tarball. I've fixed the most recent tarball and deleted all the prior ones. (Source tarballs can still be obtained directly from Fossil using the /tarball web method, of course.) Jared: You need to find the _FOSSIL_ file in the source directory and delete it. Can you give us more information about where your repository came from, Jared? -- D. Richard Hipp d...@sqlite.org -- 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] feature list?
On 10/22/11 03:44, Richard Hipp wrote: [---] -- (2) Add the ability to push/pull/sync just a specific branch, as an alternative to the current behavior of push/pull/sync of everything. The current behavior should continue as the default. Single-branch push/pull/sync should be a command-line option. -- Should this be interpreted literally: That only pull, push and sync would support specifying a subset of artifacts -- or should it be interpreted as including clone as well? Clone too. Also options to push/pull/sync/clone just wiki or tickets. Is anyone working on this? If there are no takers, I'll have a look at it. -- Kind regards, Jan Danielsson ___ 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] feature list?
Relatedly (so may be easy to do at the same time, or leave hooks to do it later), I think it might be useful to pull from a repo with a prefix added to all tags/branches. Sort of like git remote branches, to examine some changes without them being able to mess up your own state. Sent from my BlackBerry® wireless device -Original Message- From: Jan Danielsson jan.m.daniels...@gmail.com Sender: fossil-users-boun...@lists.fossil-scm.org Date: Sat, 22 Oct 2011 04:36:00 To: Fossil SCM user's discussionfossil-users@lists.fossil-scm.org Reply-To: Fossil SCM user's discussion fossil-users@lists.fossil-scm.org Subject: Re: [fossil-users] feature list? On 10/22/11 03:44, Richard Hipp wrote: [---] -- (2) Add the ability to push/pull/sync just a specific branch, as an alternative to the current behavior of push/pull/sync of everything. The current behavior should continue as the default. Single-branch push/pull/sync should be a command-line option. -- Should this be interpreted literally: That only pull, push and sync would support specifying a subset of artifacts -- or should it be interpreted as including clone as well? Clone too. Also options to push/pull/sync/clone just wiki or tickets. Is anyone working on this? If there are no takers, I'll have a look at it. -- Kind regards, Jan Danielsson ___ 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] feature list?
If I understand you correctly, Such a feature would seem to be very difficult to implement in fossil, since fossil records that information as tags on commits and doing that would necessitate either rewriting history (bad!), or to rewrite the information as its being unpacked and leave it unmodified in the database - which could lead to very surprising consequences if the repository was rebuilt. Re: syncing a subset of branches: I'm sort of tentatively looking over what it would take to modify fossil to do that. I'd like for it to be a weekend project, but I'm not overly optimistic since my weekend is pretty full at the moment. However, current thinking is that the user interface needs the following changes: 1. Several settings should be added: sync-branches, sync-tickets, sync-wiki sync-tickets and sync-wiki should be ON by default in new clones to preserve the old behavior. 2. The clone command needs to set the above to whatever you cloned with. 3. The clone/push/pull/sync commands needs to respect the new flags: --branches, --tickets, --wiki 4. specifying one of the new flags to push/pull/sync should not modify the settings 5. if you clone with --branches and --tickets, for instance, sync-wiki should be set to false, but if you only clone with --branches, sync-wiki and sync-tickets should default to on. I'm still in the process of dissecting the protocol used for sync, once that's done I'll have a better idea of what it'll take internally to extend it (and surely questions about the best way to go about that). For the moment though, I'd like thoughts on the user facing changes. -B On Fri, Oct 21, 2011 at 8:01 PM, ala...@snell-pym.org.uk wrote: Relatedly (so may be easy to do at the same time, or leave hooks to do it later), I think it might be useful to pull from a repo with a prefix added to all tags/branches. Sort of like git remote branches, to examine some changes without them being able to mess up your own state. Sent from my BlackBerry® wireless device -Original Message- From: Jan Danielsson jan.m.daniels...@gmail.com Sender: fossil-users-boun...@lists.fossil-scm.org Date: Sat, 22 Oct 2011 04:36:00 To: Fossil SCM user's discussionfossil-users@lists.fossil-scm.org Reply-To: Fossil SCM user's discussion fossil-users@lists.fossil-scm.org Subject: Re: [fossil-users] feature list? On 10/22/11 03:44, Richard Hipp wrote: [---] -- (2) Add the ability to push/pull/sync just a specific branch, as an alternative to the current behavior of push/pull/sync of everything. The current behavior should continue as the default. Single-branch push/pull/sync should be a command-line option. -- Should this be interpreted literally: That only pull, push and sync would support specifying a subset of artifacts -- or should it be interpreted as including clone as well? Clone too. Also options to push/pull/sync/clone just wiki or tickets. Is anyone working on this? If there are no takers, I'll have a look at it. -- Kind regards, Jan Danielsson ___ 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 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
