This is close to what I'm looking for. Thank you.
-Nick
On Thu, Aug 16, 2012 at 7:36 AM, Konstantin Khomoutov <
flatw...@users.sourceforge.net> wrote:
> On Wed, 15 Aug 2012 22:13:38 -0400
> Simon Tremblay wrote:
>
> > On 8/15/12 12:21 PM, Nick Zalutskiy wrote:
>
My situation:
* Working on a new feature.
* Multiple files edited.
* Notice a bug in another file, fix it.
* Decide to commit just that file with the fix.
* Type: fossil com -m "Small fix." [and crucially press enter by mistake
before specifying the file name to commit]
* ALL changes get committed
ief?
Non of this is catastrophic, but... surprised me nonetheless.
Thanks!
-Nick
On Wed, Jan 18, 2012 at 1:45 AM, Nick Zalutskiy wrote:
>
> I have setup fossil to serve repositories using inetd (xinetd in my case) as
> per http://fossil-scm.org/index.html/doc/tip/www/server.wiki
>
I have setup fossil to serve repositories using inetd (xinetd in my case)
as per http://fossil-scm.org/index.html/doc/tip/www/server.wiki
Lets say http://example.com:8585 is serving from /home/fossil/repos and
there are two fossil files in there:
repo1.fossil
repo.name.with.periods.fossil
The
I'm using fossil for the first time, on a new project -- it hurts how
pragmatic and elegant fossil is, I had to try it. Over the years, I've
developed some habits from hg and git that I can't seems to reconcile
with how fossil does things. Can somebody tell me what I'm missing or
how my workflow ne
5 matches
Mail list logo