Re: [fossil-users] Adding Fossil to Windows Explorer context menu?

2011-10-21 Thread Gilles
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

Re: [fossil-users] Creating new branch/repository problems

2011-10-21 Thread Richard Hipp
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

[fossil-users] Fossil version 1.20 released

2011-10-21 Thread Richard Hipp
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

Re: [fossil-users] Adding Fossil to Windows Explorer context menu?

2011-10-21 Thread Gilles
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

[fossil-users] feature list?

2011-10-21 Thread Jan Danielsson
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

Re: [fossil-users] feature list?

2011-10-21 Thread Dmitry Chestnykh
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

Re: [fossil-users] feature list?

2011-10-21 Thread Jan Danielsson
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?

Re: [fossil-users] feature list?

2011-10-21 Thread Richard Hipp
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

Re: [fossil-users] Creating new branch/repository problems

2011-10-21 Thread Richard Hipp
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:

Re: [fossil-users] feature list?

2011-10-21 Thread Jan Danielsson
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

Re: [fossil-users] feature list?

2011-10-21 Thread alaric
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

Re: [fossil-users] feature list?

2011-10-21 Thread Brian Smith
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