Hi,

I'm glad you solved it!

I think that "git commit -a" adds all changed to files already known by
git. Recently created files still have to be added with "git add ...".
As Kevin suggested, using "git status" a lot will save you a lot of
trouble ;).

Warm regards,
Ignacio

El 25/11/13 21:41, kevinpfromnm escribió:
> Huh, that is odd.
> 
> I'm in the habit of checking status often and manually using add before
> committing so I haven't used -a more than a couple of times.
> 
> It might be that -a limits to either new files, or changed files, or not
> new subdirectories.
> 
> On Monday, November 25, 2013 9:59:58 AM UTC-7, donz wrote:
> 
>     Hi All!
> 
>     I am having a problem (yes, another one:-[ ).  I have an app that works
>     fine on my local machine running under foreman (production mode).  I
>     uploaded the app to heroku and copied the database using pgbackup
>     locally and pgrestore on heroku.  The database contents are
>     identical as
>     far as I can tell.
> 
>     On heroku, it crashes almost immediately after starting with the error:
> 
>     uninitialized constant Showing::ShowingTiming
> 
>     pointing to the first line of:
> 
> 
>        belongs_to :showing_timing
>        belongs_to :listing, :inverse_of => :showings
>        belongs_to :client, :inverse_of => :showings
> 
>     in showing.rb
> 
>     when I comment this out and reload:
> 
>     uninitialized constant Agent::LeadNotice
> 
>     pointing to:
> 
>        has_many :lead_notices, :accessible => true
>        children :lead_notices
> 
>     in agent.rb
> 
>     When I comment this out and reload, the app no longer crashes, but
>     neither "Showing timing" nor "Lead notices" appear in the menu (they
>     are
>     there on the local machine when uncommented), and referencing them on
>     heroku then causes the app to crash (local crashes same way when run
>     with them commented out).
> 
>     I am going to try duplicating showing_timing with another name and
>     changing the reference to it in showing.rb to see if it affects
>     anything
>     (leaving the lead_notices commented out for now).  I'll post the
>     results
>     of that here when I get them.
> 
>     In the meantime, if anyone has any ideas of how to troubleshoot this
>     further, I would greatly appreciate hearing from you.
> 
>     Thanks,
> 
>     Don Ziesig
> 
> 
> 
> 
> 
> 
> -- 
> You received this message because you are subscribed to the Google
> Groups "Hobo Users" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at http://groups.google.com/group/hobousers.
> For more options, visit https://groups.google.com/groups/opt_out.

-- 
Ignacio Huerta Arteche
http://www.ihuerta.net
Teléfono: 0034 645 70 77 35
Email realizado con software libre

-- 
You received this message because you are subscribed to the Google Groups "Hobo 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/hobousers.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to