Bugs item #1726161, was opened at 2007-05-26 20:02
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=723099&aid=1726161&group_id=132078

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: website
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Jure Repinc (jrepin)
Assigned to: Nobody/Anonymous (nobody)
Summary: Post-update script doesn't like newly created branches

Initial Comment:
First I created a new local branch with cg-switch: logging
Then I created a reference to remote branch with cg-branch-add: r-logging -> 
git+ssh://[EMAIL PROTECTED]/git/parsek.git#logging
I created 3 new file in local branch and then used cg-commit and cg-push 
r-logging

I got this output:
updating 'refs/heads/logging'
  from 0000000000000000000000000000000000000000
  to   8ccef63b2fad7e0823078f398bfd085907e84765
Generating pack...
Done counting 6 objects.
Deltifying 6 objects...
 100% (6/6) done
Writing 6 objects...
 100% (6/6) done
Total 6 (delta 1), reused 0 (delta 0)
Unpacking 6 objects
fatal: bad object 0000000000000000000000000000000000000000
refs/heads/logging: 0000000000000000000000000000000000000000 -> 
8ccef63b2fad7e0823078f398bfd085907e84765

Despite the error:
fatal: bad object 0000000000000000000000000000000000000000

all seams to be OK and when I modified one one of the file and pushed again all 
was without errors.

mithro says that there is an error in our scripts:
"it appears that the post-update script doesn't like newly created branches"

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=723099&aid=1726161&group_id=132078
_______________________________________________
tp-bugs mailing list
[email protected]
http://mail.thousandparsec.net/cgi-bin/mailman/listinfo/tp-bugs

Reply via email to