On Thu, Jan 16, 2014 at 12:32:42AM +0300, Sergei Gavrikov wrote:
> Hi
>
> After this http://fossil-scm.org/index.html/info/1aef260f4c check-in I
> cannot do incremental import anymore (I get the second dup trunk). An
> imported git project is simple and has 'master' branch only. After that
> I di
On Fri, 17 Jan 2014, Sergei Gavrikov wrote:
> Excuse word "regression". s/regression/fix/. However, new handling of
> timezone offset "begins" new timeline as the previous imports have
> been done before this check-in.
If you fall in the same trap, the next filter did restore the previous
Fossil
On Thu, 16 Jan 2014, Sergei Gavrikov wrote:
> After this http://fossil-scm.org/index.html/info/1aef260f4c check-in I
> cannot do incremental import anymore (I get the second dup trunk). An
> imported git project is simple and has 'master' branch only. After that
> I did revert this check-in the l
Hi
After this http://fossil-scm.org/index.html/info/1aef260f4c check-in I
cannot do incremental import anymore (I get the second dup trunk). An
imported git project is simple and has 'master' branch only. After that
I did revert this check-in the latest Fossil build does incremental
import for th
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",
Thank you Ben, your hint did the trick for me.
> If somebody can make available to me an example git repo for which
--full-tree is required, I'll try to track down the bug.
Repo is kinda too big to send it over email, and I have no privileges to
grant you remote access, but I'll try to reproduce t
On Thu, Jun 9, 2011 at 8:26 AM, Ben Summers wrote:
>
> Alexander Vladimirov wrote:
> >
> > I tried to convert my subversion repo to fossil today and encountered a
> > problem.
> > As I can tell, svn->git conversion went ok, as I don't see the problem in
> > the resulting git repo itself.
> > Afte
Alexander Vladimirov wrote:
>
> I tried to convert my subversion repo to fossil today and encountered a
> problem.
> As I can tell, svn->git conversion went ok, as I don't see the problem in
> the resulting git repo itself.
> After doing "git fast-export --all | fossil import --git myrepo.fossil"
I tried to convert my subversion repo to fossil today and encountered a
problem.
As I can tell, svn->git conversion went ok, as I don't see the problem in
the resulting git repo itself.
After doing "git fast-export --all | fossil import --git myrepo.fossil" and
then doing "fossil open" on newly cre
On Jan 11, 2011, at 8:58 PM, Richard Hipp wrote:
>
>
> On Tue, Jan 11, 2011 at 8:44 PM, Doug Currie wrote:
>
> On Jan 11, 2011, at 6:51 PM, Richard Hipp wrote:
>
> > On Tue, Jan 11, 2011 at 4:14 PM, Doug Currie wrote:
> >
> >> I dumped my small svn repo using svn-dump-fast-export from
> >>
On Tue, Jan 11, 2011 at 8:44 PM, Doug Currie wrote:
>
> On Jan 11, 2011, at 6:51 PM, Richard Hipp wrote:
>
> > On Tue, Jan 11, 2011 at 4:14 PM, Doug Currie
> wrote:
> >
> >> I dumped my small svn repo using svn-dump-fast-export from
> http://barrbrain.github.com/
> >> and imported it using fossi
On Jan 11, 2011, at 6:51 PM, Richard Hipp wrote:
> On Tue, Jan 11, 2011 at 4:14 PM, Doug Currie wrote:
>
>> I dumped my small svn repo using svn-dump-fast-export from
>> http://barrbrain.github.com/
>> and imported it using fossil import --git
>>
>> The repo was created but all of my svn chec
On Tue, Jan 11, 2011 at 4:14 PM, Doug Currie wrote:
> I dumped my small svn repo using svn-dump-fast-export from
> http://barrbrain.github.com/
> and imported it using fossil import --git
>
> The repo was created but all of my svn checkins look like separate leaves,
> all on branch: master. There
On Tue, Jan 11, 2011 at 4:14 PM, Doug Currie wrote:
> I dumped my small svn repo using svn-dump-fast-export from
> http://barrbrain.github.com/
> and imported it using fossil import --git
>
Can you send me the output of svn-dump-fast-export via private email so that
I can troubleshoot it?
>
>
I dumped my small svn repo using svn-dump-fast-export from
http://barrbrain.github.com/
and imported it using fossil import --git
The repo was created but all of my svn checkins look like separate leaves, all
on branch: master. There is no ancestor.
If I update to the first checkin, and try to
On Mon, Apr 12, 2010 at 7:48 PM, Eric wrote:
> If you need access rights set, you include a script to set them - why
> should Fossil itself remember settings that are dependent on the target
> machine and OS?
>
Sorry, i didn't mean to imply that fossil should do that. Fossil does
remember the +x
On Mon, April 12, 2010 at 10:04 am, "Stephan Beal"
wrote:
> On Mon, Apr 12, 2010 at 4:06 AM, verizon wrote:
>
>>I'm running fossil version [2255e4e3ba] 2009-12-20 02:58:18 UTC
>> on
>> UNIX (and linux) and am trying to import about 1 Gig of files (it's a
>> Linux
>> distribution and tool
For this exercise permissions are not important (the distribution is originally
(before import) copied to my directory and is rw by me). I don't think I've
hit the 1 G limit since the while the distribution is 1 G it is made of
thousands of files so no one thing is all that large.
--ji
On Mon, Apr 12, 2010 at 4:06 AM, verizon wrote:
>I'm running fossil version [2255e4e3ba] 2009-12-20 02:58:18 UTC on
> UNIX (and linux) and am trying to import about 1 Gig of files (it's a Linux
> distribution and tool set for a propriety system).
>
Fossil lacks several features which mak
Hi,
I'm running fossil version [2255e4e3ba] 2009-12-20 02:58:18 UTC on UNIX
(and linux) and am trying to import about 1 Gig of files (it's a Linux
distribution and tool set for a propriety system). When I do this the import
works but a subsequent pull fails. There is one directory (ta
31 matches
Mail list logo
