> Depending on if your files fit a nice set of patterns you may want to
> consider using ignore-glob to keep from seeing your irrelevant files. The
> methodology I encourage on our team is that a "fossil extras" should
> always be clean, i.e. there should be no extras.
That sounds like a good idea
> > To see the list of "unmanaged" files:
> Thank you. It is more "manual" than I was looking for but if that's the way
> it works that's the way it works.
>
> Beware of any program that thinks it knows more than you do.
>
>--
>D. Richard Hipp
Point taken, but that isn't what I've been wondering
On Mon, Mar 19, 2012 at 4:00 PM, wrote:
> >
> > fossil extra
>
> > To see the list of "unmanaged" files:
> Thank you. It is more "manual" than I was looking for but if that's the way
> it works that's the way it works.
>
Beware of any program that thinks it knows more than you do.
--
D. Richa
I wrote about some of the other issues you addressed in another post.
>> What should I be doing to make sure fossil knows about all the new code?
>> add doesn't seem to work, and stat or chan doesn't flag newly created
>> files that I haven't already added.
> fossil add file
> fossil commit -m '
On Mon, Mar 19, 2012 at 4:12 AM, wrote:
[snip]
> >> I often add programs to the project and I don't always remember to tell
> >> fossil about them. What is the correct way to use fossil so when you
> work
> >> on new projects where you don't have everything that will ultimately be
> part
> >> o
>> I notice the .fossil file is created in my home directory when using
>> fossil. Because I am testing how fossil works to learn how to use it for my
>> workflows, I have created several fossil repos for different test projects
>> and then sometimes delete the whole subdirectory containing the rep
On Sun, Mar 18, 2012 at 12:10 PM, wrote:
>
> I notice the .fossil file is created in my home directory when using
> fossil. Because I am testing how fossil works to learn how to use it for my
> workflows, I have created several fossil repos for different test projects
> and then sometimes delete
On Sun, Mar 18, 2012 at 5:10 PM, wrote:
> I notice the .fossil file is created in my home directory when using
> fossil.
It will create it wherever you tell it to. e.g.:
fossil new /tmp/foo.fossil
mkdir ~/foo
cd ~/foo
f open /tmp/foo.fossil
Then ~/foo is your checkout and the repo is /tmp/foo
Hi I have been using Mercurial for my own small projects and am mostly
satisfied with it from a perspective of using it. I don't like that it uses
Perl scripts and other pieces to do what it does. I really like the fossil
and sqlite design having one standalone executable and no dependencies.
Outst
9 matches
Mail list logo
