Mark,

If you want to checkout (and track) remote branches you need to do:

git checkout -b your_cool_branch_name --track origin/next

HTH
snusnu

On Sat, Oct 24, 2009 at 04:28, MarkMT <[email protected]> wrote:
>
> Thanks Dan. It does look like this may be the problem... I am in fact
> using DO 0.10.0. However I'm not sure how to get 0.10.1 - has that
> actually been released? 'sudo gem install' produces 0.10.0 for both
> data_objects and do_mysql. And when I clone the code from github, I
> get 'master' which is also at 0.10.0 released on September 15. I may
> be running into the limits of my git knowledge - I can see on the
> github network diagram that there is a 'next' tag that is at 0.10.1,
> but it doesn't show up in the repo when I clone. What's the right way
> to get this?
>
> Mark
>
>
> On Oct 23, 7:10 pm, "Dan Kubb (dkubb)" <[email protected]> wrote:
>> Mark,
>>
>> > Thanks Dan. Here is a modified script that illustrates the problem I
>> > described.
>>
>> >http://gist.github.com/216205
>>
>> > I see the same behavior here as I did with merb.
>>
>> Here's my fork of your script including the output when running
>> against edge (git) extlib, do_mysql and dm-core:
>>
>>  http://gist.github.com/217280
>>
>> The methods return expected values, and the SQL that executes is what
>> I'd expect too.  I wonder if perhaps you are running an old version of
>> DataObjects.  You should be using DO 0.10.1 with dm-core.  Can you try
>> updating to the latest code in git and see if the problem continues?
>> If it's still not fixed, can you include the script output in your
>> gist like I have?
>>
>> --
>>
>> Dan
>> (dkubb)
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"DataMapper" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/datamapper?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to