Re: [fossil-users] Fossil 2.1

2017-03-10 Thread K. Fossil user
1/ Git is better than Fossil when it comes to the job to be done. period. 2/ nine days after first commit is not evidence of efficiency. a) it could be an evidence of issues. Windows compilation issue was reported after commits in the past.That kind of issue is totally abnormal. b) The version

Re: [fossil-users] Fossil can not import its own git export

2017-03-10 Thread Martin Gagnon
On Fri, Mar 10, 2017 at 02:02:23PM -0600, Zakero wrote: > In an effort to do some experimenting with the latest release of Fossil: > > ./fossil-2.1 version > This is fossil version 2.1 [83e3445f67] 2017-03-10 17:07:08 UT > > I wanted to export the fossil repository to git. Then import the "git

[fossil-users] Fossil can not import its own git export

2017-03-10 Thread Zakero
In an effort to do some experimenting with the latest release of Fossil: ./fossil-2.1 version This is fossil version 2.1 [83e3445f67] 2017-03-10 17:07:08 UT I wanted to export the fossil repository to git. Then import the "git file" back into fossil. Being the first time to attempt this, there

Re: [fossil-users] Fossil 2.1

2017-03-10 Thread Warren Young
On Mar 10, 2017, at 10:26 AM, Richard Hipp wrote: > > Fossil version 2.1 is now available from the download pages. …after 9 days from first commit to final release. Beat that, Git! ___ fossil-users mailing list

[fossil-users] Fossil 2.1

2017-03-10 Thread Richard Hipp
Fossil version 2.1 is now available from the download pages. Please let me know if you find any problems. The next check-in to the self-hosting Fossil repository will likely use a SHA3 hash. -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing

Re: [fossil-users] The SHA3 transition as firewall

2017-03-10 Thread Warren Young
On Mar 10, 2017, at 2:53 AM, Joerg Sonnenberger wrote: > > On Thu, Mar 09, 2017 at 01:37:35PM -0700, Warren Young wrote: >> >> >> That can be gotten around with a MITM attack > > It still only matters if you can *introduce* objects. You’re telling me it’s of no consequence if,

Re: [fossil-users] Modify username after git import

2017-03-10 Thread Joerg Sonnenberger
On Fri, Mar 10, 2017 at 12:40:34PM +, Pietro Cerutti wrote: > On 2017-Mar-10, 12:35, Joerg Sonnenberger wrote: > > On Fri, Mar 10, 2017 at 11:30:15AM +, Pietro Cerutti wrote: > > > I would like to change the user associated with commits from > > > g...@gahr.ch to simply gahr. Do to that, I

Re: [fossil-users] Modify username after git import

2017-03-10 Thread Pietro Cerutti
On 2017-Mar-10, 12:35, Joerg Sonnenberger wrote: > On Fri, Mar 10, 2017 at 11:30:15AM +, Pietro Cerutti wrote: > > I would like to change the user associated with commits from > > g...@gahr.ch to simply gahr. Do to that, I updated the 'user' column of > > the 'event' table. > > That's not

Re: [fossil-users] Modify username after git import

2017-03-10 Thread Joerg Sonnenberger
On Fri, Mar 10, 2017 at 11:30:15AM +, Pietro Cerutti wrote: > I would like to change the user associated with commits from > g...@gahr.ch to simply gahr. Do to that, I updated the 'user' column of > the 'event' table. That's not enough. You have to actually "amend" the commit. Joerg

[fossil-users] Modify username after git import

2017-03-10 Thread Pietro Cerutti
I have converted a simple git repo to fossil using git fast-export --all | fossil import --git tcl-scgi.fossil I would like to change the user associated with commits from g...@gahr.ch to simply gahr. Do to that, I updated the 'user' column of the 'event' table. Both fossil timeline and

Re: [fossil-users] The SHA3 transition as firewall

2017-03-10 Thread Joerg Sonnenberger
On Thu, Mar 09, 2017 at 01:37:35PM -0700, Warren Young wrote: > On Mar 9, 2017, at 1:03 PM, Richard Hipp wrote: > > > > If a new artifact Y' which has the > > same SHA1 hash as Y comes along, it will be discarded, since an > > artifact with that same hash is already in the