Thanks for clarifying that. So I guess it would be either release note
advise or schema change notification when running maybe even
any command, if it was up to me. ;)
Pozdrawiam / With best regards,
Orzech
W dniu 13.12.2015 o 22:58, Joerg Sonnenberger pisze:
> I wouldn't advise to run it after e
On Sun, Dec 13, 2015 at 09:57:44PM +0100, Piotr Orzechowski wrote:
> I guess it would be better to change help message about rebuild then.
> As of now, it says "Run this command after updating the fossil
> executable in a way that changes the database schema." So I would
> expect to see some inform
I guess it would be better to change help message about rebuild then.
As of now, it says "Run this command after updating the fossil
executable in a way that changes the database schema." So I would
expect to see some information about such need in release notes.
Perhaps it would be better to add t
On 13 December 2015 at 05:12, Piotr Orzechowski wrote:
> I've just looked at release notes for 1.34 and 1.33 and there was no
> straightforward note about need to rebuild repositories.
Admittedly I don't do it every time, but I thought that was something
to be done for every update?
Here's ope
On Sun, Dec 13, 2015 at 02:12:01PM +0100, Piotr Orzechowski wrote:
> I've just looked at release notes for 1.34 and 1.33 and there was no
> straightforward note about need to rebuild repositories. Maybe it would
> be better to add such information to requiring release notes, or maybe
> even fossil
I've just looked at release notes for 1.34 and 1.33 and there was no
straightforward note about need to rebuild repositories. Maybe it would
be better to add such information to requiring release notes, or maybe
even fossil would be able to suggest repo rebuilding itself?
Pozdrawiam / With best re
On 2015-12-12T16:06:20 -0800
jungle Boogie wrote:
>
> Great news!
>
> Did you happen to change your git version at all during either test?
Nope, same version all along (2.6.2).
M
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://
On 12 December 2015 at 14:48, wrote:
> Ah!
>
> I've just discovered that if I use the trunk version of fossil and run
> it on a freshly created repository, then it does export correctly. If I
> use the trunk version of fossil on the repository created by the older
> version, it fails. If I 'fossi
On 2015-12-12T17:14:56 -0500
Martin Gagnon wrote:
>
> For some reason, mine have an extra line at the end that look like this:
>
> M 100644 :10 README-b0.txt
>
> For the rest, it's pretty similar.
Ah!
I've just discovered that if I use the trunk version of fossil and run
it on a freshly creat
On Sat, Dec 12, 2015 at 10:09:26PM +, org.fossil-scm.fossil-us...@io7m.com
wrote:
> On 2015-12-12T21:43:49 +
> wrote:
>
> > On 2015-12-12T16:21:14 -0500
> > Martin Gagnon wrote:
> > > >
> > > > The script you've attached is exactly what I used to create the test
> > > > case. Which ver
On 2015-12-12T21:43:49 +
wrote:
> On 2015-12-12T16:21:14 -0500
> Martin Gagnon wrote:
> > >
> > > The script you've attached is exactly what I used to create the test
> > > case. Which versions are you using?
> >
> > This is fossil version 1.34 [a4889252f1] 2015-12-07 18:19:28 UTC
> >
> >
On 2015-12-12T16:21:14 -0500
Martin Gagnon wrote:
> >
> > The script you've attached is exactly what I used to create the test
> > case. Which versions are you using?
>
> This is fossil version 1.34 [a4889252f1] 2015-12-07 18:19:28 UTC
>
> git version 1.9.1
Hrm, fossil is quite a bit newer and
On Sat, Dec 12, 2015 at 09:18:12PM +, org.fossil-scm.fossil-us...@io7m.com
wrote:
> On 2015-12-12T16:07:23 -0500
> Martin Gagnon wrote:
> >
> > What version of git and fossil are you using ?
> >
> > I cannot reproduce the problem using your repo case. After the merge,
> > the README-b0.txt
On 2015-12-12T23:24:08 +0300
Konstantin Khomoutov wrote:
>
> Did you report a bug?
>
> It's just a matter of posting a mail to git at vger.kernel.org;
> subscription is not required.
I sent the git list the same info and test case a couple of hours ago,
but haven't had a response yet.
I still
On 2015-12-12T16:07:23 -0500
Martin Gagnon wrote:
>
> What version of git and fossil are you using ?
>
> I cannot reproduce the problem using your repo case. After the merge,
> the README-b0.txt file is present.
>
> Here a script that reproduce your repo case, does it correspond to your
> test
On Sat, Dec 12, 2015 at 02:47:59PM +, org.fossil-scm.fossil-us...@io7m.com
wrote:
> On 2015-12-12T14:21:19 +
> wrote:
> >
> > Ideally, I'd be able to reproduce this with a somewhat smaller
> > repository...
>
> Surprisingly, this turned out to be easier than expected!
>
> http://waste.
On Sat, 12 Dec 2015 08:42:48 -0500
Richard Hipp wrote:
> > It seems that somebody else ran into this at the start of the year:
> > http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg19238.html
> Yeah, that's a bummer.
>
> Part of the problem stems from the fact that the Git fast-ex
Tnx for the repro case! I'm away from office most of today. Will
look when I'm able.
On 12/12/15, org.fossil-scm.fossil-us...@io7m.com
wrote:
> On 2015-12-12T14:21:19 +
> wrote:
>>
>> Ideally, I'd be able to reproduce this with a somewhat smaller
>> repository...
>
> Surprisingly, this tur
On 2015-12-12T14:21:19 +
wrote:
>
> Ideally, I'd be able to reproduce this with a somewhat smaller
> repository...
Surprisingly, this turned out to be easier than expected!
http://waste.io7m.com/2015/12/12/fossilexport/
1. Create fossil repository.
2. Add README.txt and commit in trunk.
3.
On 2015-12-12T08:42:48 -0500
Richard Hipp wrote:
>
> The import/export functionality of Fossil has been greatly improved in
> the past by the work of volunteers tracking down obscure
> incompatibilities. If you would like to try to get to the bottom of
> the problems you are seeing, and either i
On 12/12/15, org.fossil-scm.fossil-us...@io7m.com
wrote:
> On 2015-12-12T12:26:19 +
> wrote:
>>
>> Is there some way to get more information about what's going wrong here? I
>> don't
>> know if fossil or git is at fault, and I have no way of knowing how badly
>> the
>> history has been corrup
On 2015-12-12T12:26:19 +
wrote:
>
> Is there some way to get more information about what's going wrong here? I
> don't
> know if fossil or git is at fault, and I have no way of knowing how badly the
> history has been corrupted by the export or import.
It seems that somebody else ran into th
Hello!
I'm attempting to export a moderately large (241mb) repository to git:
http://fossil.io7m.com/repo.cgi/io7m-r1/index
The export proceeds without an error:
/tmp/r1-fossil$ fossil export > /tmp/r1.bin
The import proceeds without an error:
/tmp/r1-git$ git init
/tmp/r1-git$ git fa
23 matches
Mail list logo
