Re: [fossil-users] Cutting fossil repository

[Adam Jensen]

On 10/08/2016 06:40 PM, Richard Hipp wrote:
> I do not know how to make the documentation any clearer.

It's something I've been thinking about [in general] for a while and I
just used this opportunity to inject the idea into the Fossil community.
This seems like the sweet spot with TCL on one side (terrible
documentation/organization) and SQLite on the other (stellar software
engineering).

___
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] Removing dangling links to checkouts

[Andy Bradford]

Thus said Thomas Levine on Sat, 08 Oct 2016 10:23:24 -:

> Suppose that some of a  repository's checkout references are no longer
> valid.
>
> The question:  Is there  a good way  to remove the  dead ones?  I have
> already reviewed them to determine that it is safe to remove them.

Fossil automatically removes references to stale checkouts:

$ fossil all ls -c | grep new
/tmp/new/
$ rm -rf /tmp/new
$ fossil all ls -c | grep new
$ 

Andy
-- 
TAI64 timestamp: 400057f97649


___
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] Cutting fossil repository

[Richard Hipp]

On 10/8/16, Adam Jensen  wrote:
>
> The reluctance of some programmer communities to provide examples has
> always surprised me.

In this case, the documentation
(https://www.fossil-scm.org/fossil/help?cmd=purge) consists of a
series of examples, each followed by an explanation of what that
example does.

I do not know how to make the documentation any clearer.
Contributions from others who do know how to make better documentation
will be greatly appreciated.

-- 
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] Cutting fossil repository

[Adam Jensen]

On 10/08/2016 02:23 PM, Zeev Pekar wrote:
> Ok. I understood the consequences - I'll operate on a copy of a repo. So
> could you, please, provide the two examples anyway?

*snide humor alert*

The reluctance of some programmer communities to provide examples has
always surprised me. I think documentation would be much more effective
if there were comprehensive examples throughout. It seems like those
comprehensive examples could be written in a way such that they could be
executed as part of the test suite, mostly as a way to verify that the
documentation is still in sync with the source.

But I come from an electrical engineering education where the goals are
to create clear, concise understandings in the most efficient and
effective way. Open source software communities seem to have different
values/cult'ure.

___
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] Unversioned files.

[Arseniy Terekhin]

Really like unversioned files feature.

On windows you can't do 'fossil uv add ajax\index.html', only forward
slashes will work. Which is okay, but I'd prefer fossil to do slash
replacing.

On Tue, Aug 30, 2016 at 9:31 PM, Richard Hipp  wrote:

> A new feature of Fossil (currently unreleased and only available to
> people who are willing to recompile the code on trunk) is "unversioned
> files".
>
> https://www.fossil-scm.org/fossil/doc/trunk/www/unvers.wiki
>
> The "Download" page on the canonical Fossil website is now implemented
> using these unversioned files, which means that mirrors that sync with
> the -u option also mirror the Download page content.
>
> Your feedback on this new feature is appreciated.
>
> --
> 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
>



-- 
I remain,
Arseniy Terekhin
___
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 plugin for QtCreator IDE

[Artur Shepilko]

We finally got to release Fossil plugin for QtCreator:
https://github.com/nomadbyte/qtcreator-plugin-fossil

The Fossil plugin is free and open-source, of course. The README describes
how to build it. The most recent QtCreator version we used it with is
QtCreator-4.0.1, which is included in Qt 5.6.1-1 LTS (long-time support)
release. Through its life, internally we used the plugin with previous
versions of both QtCreator and Fossil client (the most recent was 1.35).

Hope this would help further spread the use of Fossil SCM, which is hard to
over-praise for its simplicity and versatility. Notably, thanks to Fossil
core devs for advancing its features over the years -- we really
appreciated this (first plugin release used fossil 1.26)

For folks not familiar with QtCreator -- it's a multi-platform IDE for
C/C++ development. Primarily it targets Qt-based projects, but it's also
used with non-Qt projects and supports CMake-based projects. Support for
several popular SCMs is already built-in, yet Fossil is not supported --
with this plugin it is!

Fossil plugin adds Fossil SCM as a choice for version control to use with
projects (similar to git, bazaar etc.). It's implemented using QtCreator
VCS framework which calls Fossil command-line interface. It supports
create/clone project repo, add/delete/rename files, diff/annotate,
status/timeline, revert/update/pull/push. Base set of operations, but it's
sufficient in routine development, the rest can be done directly with
fossil command.

Enjoy!

Artur
___
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] Cutting fossil repository

[Zeev Pekar]

1) But what about the first case? Is the following correct:

fossil purge artifacts 86848307235407

2) can I  delete several commits like this:

fossil purge artifacts 86848307235407 563453457234 56488921223

Thanks.

On Sat, 2016-10-08 at 14:58 -0400, Richard Hipp wrote:
> On 10/8/16, Zeev Pekar  wrote:
> >
> > 2) using shun:
> >
> > fossil shun 86848307235407 (this is just a guess since this one I
> > couldn't find in docs)
> >
> > Am I right?
> 
> There is no "shun" command.  Shunning must be done from the web interface.

___
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] Cutting fossil repository

[Richard Hipp]

On 10/8/16, Zeev Pekar  wrote:
>
> 2) using shun:
>
> fossil shun 86848307235407 (this is just a guess since this one I
> couldn't find in docs)
>
> Am I right?

There is no "shun" command.  Shunning must be done from the web interface.
-- 
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] Cutting fossil repository

[Zeev Pekar]

Ok, so let me try... Let's say we want to delete a commit 86848307235407

1) using purge it should be:

fossil purge artifacts 86848307235407

2) using shun:

fossil shun 86848307235407 (this is just a guess since this one I
couldn't find in docs)

Am I right?

Thank you.

On Sat, 2016-10-08 at 14:28 -0400, Richard Hipp wrote:
> On 10/8/16, Zeev Pekar  wrote:
> > Ok. I understood the consequences - I'll operate on a copy of a repo. So
> > could you, please, provide the two examples anyway?
> >
> 
> I do not know how to improve upon
> https://www.fossil-scm.org/fossil/help?cmd=purge
> 
> If you can explain what part of the documentation is unclear, perhaps
> we can clarify it for you.
> 

___
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] Cutting fossil repository

[Richard Hipp]

On 10/8/16, Zeev Pekar  wrote:
> Ok. I understood the consequences - I'll operate on a copy of a repo. So
> could you, please, provide the two examples anyway?
>

I do not know how to improve upon
https://www.fossil-scm.org/fossil/help?cmd=purge

If you can explain what part of the documentation is unclear, perhaps
we can clarify it for you.

-- 
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] Cutting fossil repository

[Zeev Pekar]

Ok. I understood the consequences - I'll operate on a copy of a repo. So
could you, please, provide the two examples anyway?

Thank you.


On Sat, 2016-10-08 at 14:19 -0400, Richard Hipp wrote:
> On 10/8/16, Zeev Pekar  wrote:
> > Could somebody, please, provide an example of deleting a commit, using
> > a) purge
> > b) shun
> >
> 
> If you need an example in order to pull this off, then it is not
> something you should attempt.  The use of purge and shun is for
> experts only.  If you do not have a full understanding of what you are
> doing, you will likely end up making a mess.
> 
> Fossil is designed to never forget things.  You are asking it to
> forget, which goes against its very nature.  Some provisions are made
> for this, for exceptional circumstances.  But those provisions are
> very seldom used, and are not novice-friendly.
> 
> 

___
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] Cutting fossil repository

[Richard Hipp]

On 10/8/16, Zeev Pekar  wrote:
> Could somebody, please, provide an example of deleting a commit, using
> a) purge
> b) shun
>

If you need an example in order to pull this off, then it is not
something you should attempt.  The use of purge and shun is for
experts only.  If you do not have a full understanding of what you are
doing, you will likely end up making a mess.

Fossil is designed to never forget things.  You are asking it to
forget, which goes against its very nature.  Some provisions are made
for this, for exceptional circumstances.  But those provisions are
very seldom used, and are not novice-friendly.


-- 
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] Cutting fossil repository

[Zeev Pekar]

Could somebody, please, provide an example of deleting a commit, using
a) purge
b) shun

Thank you in advance!
Zeev


On Fri, 2016-10-07 at 15:57 -0400, Richard Hipp wrote:
> On 10/7/16, sky5w...@gmail.com  wrote:
> > Cool.
> > How does 'fossil purge obliterate' differ from 'fossil shun'?
> 
> "shun" rmembers the SHA1 hash and will never again accept that SHA1
> hash on a sync.  "fossil purge whatever" simply deletes the artifacts
> from the local repo.  They will be restored on a sync from another
> repo that holds them.
> 
> I think.  Double-check before relying on what I said above.  :-)
> 
> > Is shun obsoleted or superseded by purge now?
> > Can I achieve the obliteration entirely from the cmd line?
> >
> > Thanks!
> >
> 
> 

___
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] incremental Git import

[Nickolas Lloyd]

Nickolas Lloyd  writes:

> I see that this is missing from
> c79d278db1119360497f6fb4b2f62de94ed38135.  Thanks for catching that!
> I'll go ahead and update it with this information.
>
>> BTW, here https://www.fossil-scm.org/index.html/artifact/c79d278db1119360
>> is missing "../repo.fossil" at the end of `git fast-export ...`
> Ditto.

Pushed in commit [880e3fb51f] to nick.lloyd-git-interop branch.  Does
this sufficiently address the original concerns?

>> and nick.lloyd-git-interop version cannot export to git,
*snip*
> Is this behavior new to this branch?  I haven't actually looked much at
> how tags are handled.  I'll see if I can reproduce this and create a fix.

This was indeed a regression introduced in the nick.lloyd-git-interop
branch.  Just pushed a fix in [b2e0fda9e1].  Please let me know if you
still observe problems.

Thanks,
Nick
___
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] incremental Git import

[Nickolas Lloyd]

Svyatoslav Mishyn writes:

> Hello,
>
> it looks that incremental git import doesn't work:
*snip*
> git fast-export --import-marks=../git.marks --export-marks=../git.marks \
>   | fossil import --git --incremental   \
>   --import-marks ../fossil.marks --export-marks ../fossil.marks \
>   ../test.fossil
You'll need to specify which revisions to export as part of the git
command.  See git-fast-export(1), specifically:
  [...]
  A list of arguments, acceptable to git rev-parse and git rev-list,
  that specifies the specific objects and references to export. For
  example, master~10..master causes the current master reference to
  be exported along with all objects added since its 10th ancestor
  commit.
In this case `trunk' would do the trick, or `--all'.

I see that this is missing from
c79d278db1119360497f6fb4b2f62de94ed38135.  Thanks for catching that!
I'll go ahead and update it with this information.

> BTW, here https://www.fossil-scm.org/index.html/artifact/c79d278db1119360
> is missing "../repo.fossil" at the end of `git fast-export ...`
Ditto.

> and nick.lloyd-git-interop version cannot export to git,
> if checkin has a few tags:
> fatal: mark :7 not declared
> fast-import: dumping crash report to .git/fast_import_crash_1012
> Unpacking objects: 100% (5/5), done.
Is this behavior new to this branch?  I haven't actually looked much at
how tags are handled.  I'll see if I can reproduce this and create a fix.

Thanks for the feedback.

-Nick
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] incremental Git import

[Svyatoslav Mishyn]

Hello,

it looks that incremental git import doesn't work:

f ver
This is fossil version 1.36 [e727b3d50b] 2016-10-06 18:56:51 UTC
f init test.fossil && mkdir test && cd test && f open ../test.fossil
date > z
f add z
f ci -m c1

mkdir ../test.git && cd ../test.git && git init
f export --git --export-marks ../fossil.marks ../test.fossil \
  | git fast-import --export-marks=../git.marks
git co trunk
date >> z
git ci -am c2
git fast-export --import-marks=../git.marks --export-marks=../git.marks \
  | fossil import --git --incremental   \
  --import-marks ../fossil.marks --export-marks ../fossil.marks \
  ../test.fossil

f time -R ../test.fossil
=== 2016-10-08 ===
09:50:24 [928031189b] c1 (user: juef tags: trunk)
09:49:45 [f9f6644267] initial empty check-in (user: juef tags: trunk)
+++ no more data (2) +++

git --no-pager log --pretty=format:"%aD %s%n"
Sat, 8 Oct 2016 12:52:27 +0300 c2
Sat, 8 Oct 2016 09:50:24 + c1
Sat, 8 Oct 2016 09:49:45 + initial empty check-in


BTW, here https://www.fossil-scm.org/index.html/artifact/c79d278db1119360
is missing "../repo.fossil" at the end of `git fast-export ...`

and nick.lloyd-git-interop version cannot export to git,
if checkin has a few tags:
fatal: mark :7 not declared
fast-import: dumping crash report to .git/fast_import_crash_1012
Unpacking objects: 100% (5/5), done.


Thanks.


-- 
I am not a native English speaker,
so feel free to correct any spelling or grammatical errors!


signature.asc
Description: PGP signature
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Removing dangling links to checkouts

[Thomas Levine]

Suppose that some of a repository's checkout references are no longer
valid.

$ fossil version
This is fossil version 1.35 [3aa86af6aa] 2016-06-14 11:10:39 UTC
$ sqlite3 horetu.fossil "select * from config where name like 'ckout%';"
ckout:/directory/does/not/exist/anymore/|1|1463006565
ckout:/home/tlevine/horetu/|1|1475658284

The question: Is there a good way to remove the dead ones? I have
already reviewed them to determine that it is safe to remove them.

This may also be against the fossil spirit; it may be more coherent to
expect users to check whether each checkout is indeed still a checkout
before doing anything with the directory.

In my case, it turned out that there was a better way that did not
require access to the checkouts. In an earlier version of my
implementation of the missing "fossil all configuration push" in sh, I
ran "cd" on the checkout directory and then ran "fossil config push"
from there. This produced errors on missing directories, leading me to
wonder how to remove them.
http://src.thomaslevine.com/rc/info/e1c590fa8f233a554caab90b932a356456d7b9e4?txt=1=14

But I have since fixed my "fossil-all-configuration-push" to use -R.
http://src.thomaslevine.com/rc/artifact/f6fad8431281ad7d
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Correction of errors in the documentation of the -R flag to the push and sync commands

[Thomas Levine]

Before this check-in, the documentation incorrectly repeats -R flag
documentation for the "pull" command in the -R flag documentation for
the "push" and "sync" commands. This change adds accurate documentation
for the "push" and "sync" commands. Additionally, I explicitly state in
all three documentation lines that the -R flag corresponds to the local
repository, as I think this makes it easier to understand what the flag
does. The local versus remote distinction is already established at the
beginning of the documentation for each of these commands.
http://src.thomaslevine.com/fossil/ci/ddf566bceb203948?sbs=1
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users