On 12/22/13, 8:41 PM, 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
Was there ever a decision on this? I'd rather like to g
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
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 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
On 20/12/13 22:41, Jan Nijtmans wrote:
[...]
> In fossil that's not a problem: You can always move the commit to
> another branch, even after you already committed it.
Oh, yeah, I'd forgotten you could do that. Admittedly, I only noticed
after I'd done the sync, and wanted to fix things as quickly
2013/12/20 David Given :
> (Sorry, I accidentally committed to trunk and then had to undo. It'd be
> nice if 'fossil branch new' would either change the current branch or at
> the very least print a warning that the current branch hadn't changed.)
In fossil that's not a problem: You can always mov
On 20/12/13 16:15, Ron Wilson wrote:
[...]
> Interesting. I would have thought all time stamps in git would, like
> Fossil, be seconds from the epoch. (It was originally developed
> by the Linux kernel core team.)
So would I. I suppose it *is* seconds since epoch... but they don't
define which epo
On Fri, Dec 20, 2013 at 10:53 AM, David Given wrote:
> fossil import --git ignores the timezone field on timestamps. I have
> this in the fast import dump:
>
> mark :4
> author David Given 1309983972 +0100
> committer David Given 1309983972 +0100
> data 17
> Initial checkin.
>
Interesting. I w
fossil import --git ignores the timezone field on timestamps. I have
this in the fast import dump:
mark :4
author David Given 1309983972 +0100
committer David Given 1309983972 +0100
data 17
Initial checkin.
...but in the fossil repo it actually ends up being:
{
"type":"checkin",
12 matches
Mail list logo
