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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
18 matches
Mail list logo