2013/12/23 Andy Bradford :
> Hello,
>
> When clicking on the genealogy links from the /info page for a hidden
> check-in (e.g. family, ancestors, descendants, branch), the timeline
> does not display the hidden content which makes the view for hidden
> artifacts less useful and there
Hello,
When clicking on the genealogy links from the /info page for a hidden
check-in (e.g. family, ancestors, descendants, branch), the timeline
does not display the hidden content which makes the view for hidden
artifacts less useful and there is no way to unhide it except by
On Sun, Dec 22, 2013 at 9:57 PM, wrote:
> Really, I am only implying some minimal file statistic like 'DeltaSize(%)'
> or somesuch to show the user it is in fact compared internally. The current
> message contradicts what is in fact happening. Maybe change that message to
> "Cannot visually displ
On 22/12/13 20:56, Martin Gagnon wrote:
[...]
> You can use this vim plugin:
>
>
> https://code.google.com/p/lh-vim/source/browse/misc/trunk/plugin/local_vimrc.vim
Ah! I didn't know such a thing existed. Thanks, very useful.
--
┌─── ｄｇ＠ｃｏｗｌａｒｋ．ｃｏｍ ─ http://www.cowlark.com ─
│ "There
On Sun, Dec 22, 2013 at 08:41:45PM +, David Given wrote:
> On 22/12/13 20:18, Richard Hipp wrote:
> [...]
> > No. Look at the diff. The indentation is wrong.
>
> Oops, sorry. This one should fix it:
>
> http://www.fossil-scm.org/index.html/info/70b82e8cc5
>
> (Incidentally, at some future
Really, I am only implying some minimal file statistic like 'DeltaSize(%)'
or somesuch to show the user it is in fact compared internally. The current
message contradicts what is in fact happening. Maybe change that message to
"Cannot visually display binary diffs. DeltaSize(%) = -10".
On Sun, De
On Sun, Dec 22, 2013 at 3:41 PM, David Given wrote:
>
> (Incidentally, at some future point when I have time, would a patch to
> add vim modelines to all the sourcefiles be likely to be accepted? This
> would configure vim to get the indentation right automatically. I don't
> know whether emacs w
On 22/12/13 20:18, Richard Hipp wrote:
[...]
> No. Look at the diff. The indentation is wrong.
Oops, sorry. This one should fix it:
http://www.fossil-scm.org/index.html/info/70b82e8cc5
(Incidentally, at some future point when I have time, would a patch to
add vim modelines to all the sourcefil
On Sun, Dec 22, 2013 at 3:11 PM, David Given wrote:
> On 20/12/13 17:07, David Given wrote:
> [...]
> > http://www.fossil-scm.org/index.html/info/10f9673a25
>
> Does that patch look good enough to merge to trunk? If I don't do it
> today I will forget about it completely...
>
No. Look at the d
On Sun, Dec 22, 2013 at 9:06 PM, wrote:
> Thanks. I didn't know how binary was handled given the Timeline diff
> response = "cannot compute difference between binary files".
>
That message is a bit misleading. It really means a "visual difference."
There isn't a mechanism to show a textual diff
On 20/12/13 17:07, David Given wrote:
[...]
> http://www.fossil-scm.org/index.html/info/10f9673a25
Does that patch look good enough to merge to trunk? If I don't do it
today I will forget about it completely...
--
┌─── ｄｇ＠ｃｏｗｌａｒｋ．ｃｏｍ ─ http://www.cowlark.com ─
│ "There does not now, nor
Thanks. I didn't know how binary was handled given the Timeline diff
response = "cannot compute difference between binary files".
I think it would be cool if instead fossil listed some of the metrics used
or determined in the binary delta operation.
Thanks for Fossil!
On Sun, Dec 22, 2013 at 2:5
On Sun, Dec 22, 2013 at 8:44 PM, wrote:
> Ah, is there a way to quantify the binary delta?
> If I have a 1MB binary file and commit a 1 byte change, what is the size
> of the computed binary delta?
>
Very, very small:
Create two binaries with a one-byte difference:
[stephan@host:~/cvs/fossil/l
Ah, is there a way to quantify the binary delta?
If I have a 1MB binary file and commit a 1 byte change, what is the size of
the computed binary delta?
You are correct of course, but I tend not to extend the spirit of fossil to
binary files and images. It is their existence and not legacy that is
On Sun, Dec 22, 2013 at 7:37 PM, wrote:
> I am curious what is stored in the repo for each new commit that includes
> a tiny change to a binary file.
> Whether a dll or an image file, is fossil storing each binary file
> compressed, uncompressed or some sort of delta?
> Over time(6mo's to 1yr), I
On Sun, Dec 22, 2013 at 1:37 PM, wrote:
> I am curious what is stored in the repo for each new commit that includes
> a tiny change to a binary file.
> Whether a dll or an image file, is fossil storing each binary file
> compressed, uncompressed or some sort of delta?
>
A binary delta.
> Ove
I am curious what is stored in the repo for each new commit that includes a
tiny change to a binary file.
Whether a dll or an image file, is fossil storing each binary file
compressed, uncompressed or some sort of delta?
Over time(6mo's to 1yr), I would like to reduce my repo size by purging
really
On 22/12/2013 0:55, Roy Marples wrote:
On 21/12/2013 21:11, Roy Marples wrote:
I'm trying to move my dhcpcd git repository [1] to fossil [2].
While it works for the most part, it seems that the branches called
"trunk" and "dhcpcd-5" have the same commits, which is just wrong.
By adding a commi
This isn't really baked yet, but I'm off on holiday tomorrow and when I
get back I start a (highly prestigious!) new job, so I won't be able to
touch this for a while.
fhg is a bidirectional, incremental Mercural/fossil synchroniser. It'll
push changes in both directions between a Mercurial reposi
19 matches
Mail list logo
