Hi Pawel,
Thanks very much.
Brgds,
Jeroen
On Mon, May 5, 2014 at 2:00 PM, Paweł Pierzchała wrote:
> Hi Jeroen,
> thank you for for tracing that. It is fixed now in the master branch.
>
> Cheers,
> Pawel
>
>
> On 30 April 2014 14:42, Jeroen Muis wrote:
>
>> Hi,
>>
>> I've created an issue at:
Hi Jeroen,
thank you for for tracing that. It is fixed now in the master branch.
Cheers,
Pawel
On 30 April 2014 14:42, Jeroen Muis wrote:
> Hi,
>
> I've created an issue at:
> https://gitorious.org/projects/gitorious/issues/444
> as we now have a reproducible issue. It's caused by any empty co
Hi,
I've created an issue at:
https://gitorious.org/projects/gitorious/issues/444
as we now have a reproducible issue. It's caused by any empty commit
message.
Confirmed by executing git filter-branch after which the issue disappears.
$ git filter-branch --msg-filter '
message=`cat`
if [ "$messa
Hi,
Most likely I found the issue.
The initial commit (again, converted from Mercurial) has no files and an
empty commit message. Please, don't ask why and how :)
I can imagine, this might somehow be an issue for gitorious as there is
'not so much' to be displayed when the commit message is empty
Hi Pawel,
Sounds like a lot of work indeed.
I believe I do have some small repo containing this issue, so let me sort
it and revert as soon as I have some update on this topic.
FYI the are originating from Mercurial and have been converted to GIT.
Thanks for your help so far.
Jeroen
On Mon, Ap
Hi Jeroen,
I would start with creating another repo with a clone, firstly I would
remove all the branches except master to find whether the issue is related
to branching or specific commit in history.
If the tree view works, then I would try to find the broken branch by
adding them back until tree
Hi Pawel,
Thanks for your reply.
[We are accessing the 'source code' tab through the following URLs:
https://git.copasbv.lan/edi/edistep/source/master:
https://git.copasbv.lan/copas/activitygrid/source/bf31463f959d09805ebcf99e2bd0f7e030b681a1:
And yes, it's always the same repos with this issue,
Hi Jeroen,
I haven't seen that error before, so I need more details. How are you
accessing the tree history (gitorious.local/project/repository/graph)? Does
it happen all the time for the same repos? Could you prepare a repository
with a broken tree history, so we could reproduce it?
Cheers,
Pawel
Hi,
We recently started using Gitorious for managing our GIT repositories and so
far everything is running really well. Our setup seems to be pretty ok (Centos
6.5 / ce_installer) as push / fetch / branching and tagging all works.
However on some repos(not all!) the tree history doesn't load