It worked perfectly! thanks!
Also the timeline clearly shows what happened ;)
https://pizzahack.eu/fossil/thunderchez/timeline
On 05/12/2016 23:01, Tony Papadimitriou wrote:
> The following steps should work assuming you haven't added any more
> commits
> after the mistake (and haven't pushed
The following steps should work assuming you haven't added any more commits
after the mistake (and haven't pushed your changes anywhere else). Also,
your current checkout is the one with the mistake (if not, first do F UP to
the appropriate check-in):
f co prev --keep
f pur ch tip
f com file1
The following steps should work assuming you haven't added any more commits
after the mistake (and haven't pushed your changes anywhere else). Also,
your current checkout is the one with the mistake (if not, first do F UP to
the appropriate check-in):
f co prev --keep
f pur ch tip
f com
Hi,
By mistake I've made an error and did fossil commit -m "added lalal"
without specifying which files to commit, so it commited all the changed
files... but my intention was to commit only some files...
There is a way to elegantly undo the commit or modify it so as to
exclude some files?
Thanks
On Dec 4, 2016, at 12:50 PM, Karel Gardas wrote:
>
> On Sun, Dec 4, 2016 at 5:28 AM, Martin Vahi wrote:
>> It is about 4.4GiB, over 100k files, over 6k folders,
>> but it should not be that bad. After all, that's what
>> many projects look like in
As it turns out, I already made a mistake
at the tree based algorithm.
The old, proposed, flawed version:
> ...
> array_of_nodes_with_wrong_x_node_hash=unique_by_node_ID(
> clone(
> ob_AVL_tree.array_of_nodes_that_had_changes_on_path_2_root
>
> De : Joerg Sonnenberger
> À : fossil-users@lists.fossil-scm.org
> Envoyé le : Dimanche 4 décembre 2016 20h55
> Objet : Re: [fossil-users] Bug report: Terrible Performance, when
Checking in LLVM Source
> ...
> No. What repo checksum does is compute a separate checksum over
7 matches
Mail list logo