Attention Judofyr: Broken cookies in 2.0

[Aníbal Rojas]

Use the -m switch

-- 
Aníbal

On Fri, Jun 6, 2008 at 9:42 PM, Bluebie, Jenna
<blueberry at creativepony.com> wrote:
> git forced me in to vim when I did git commit -a. Turns out that's what it
> defaults to when EDITOR enviroment variable isn't set. Now it is, all is
> well.
>
>
> On 06/06/2008, at 12:11 PM, Eric Mill wrote:
>
>> How did you end up in vim?  You don't need to use any particular
>> editor, edit the files from the repository any way you want.  You
>> don't actually have to make all your changes from the command line.
>>
>> -- Eric
>>
>> On Thu, Jun 5, 2008 at 10:07 PM, Bluebie, Jenna
>> <blueberry at creativepony.com> wrote:
>>>
>>> I did some vimtutor and put some text in the thing and then :wq to save
>>> it
>>> and then it says:
>>>
>>>> fatal: There was a problem with the editor vi.
>>>
>>>
>>> A fantastic descriptive error if ever I did see one.
>>>
>>> can someone tell me how the heck to make vim go? Or better yet how to
>>> hack
>>> git to use TextMate or Coda instead?
>>>
>>>
>>> On 06/06/2008, at 11:54 AM, Bluebie, Jenna wrote:
>>>
>>>> now it's in vim and I don't know what to do and it wont let me quit and
>>>> wont save...
>>>> On 06/06/2008, at 11:35 AM, _why wrote:
>>>>
>>>>> On Fri, Jun 06, 2008 at 11:18:22AM +1000, Bluebie, Jenna wrote:
>>>>>>
>>>>>> If someone wants to tell me how git works, I'll be happy to patch
>>>>>> these
>>>>>> problems myself, provided it isn't a stressful or excessively
>>>>>> difficult
>>>>>> thing to do... My username on there is Bluebie. I have no idea how to
>>>>>> use
>>>>>> it.
>>>>>
>>>>> Basically what you need to do is fork the project, add your changes,
>>>>> commit, and send me a pull request.  The "pull request" is just a
>>>>> message that you have some changes to pick up.  It's like putting up
>>>>> the little flag on your mailbox to tell the mailman to stop by.
>>>>>
>>>>> First off, go here: http://github.com/why/camping/tree/master.
>>>>> And click the "fork" button.
>>>>>
>>>>>> From there, you'll need to do the rest from a console:
>>>>>
>>>>> $ git clone git at github.com:Bluebie/camping.git
>>>>> $ cd camping
>>>>> # ... make your changes ...
>>>>>
>>>>> $ git commit -a
>>>>> # ... saves your changes ...
>>>>>
>>>>> $ git push
>>>>> # ... sends your changes to github ...
>>>>>
>>>>> And then, you can just send me a pull request.  Go to your camping
>>>>> page: http://github.com/Bluebie/camping/tree/master.  Click on "pull
>>>>> request" and explain the change.
>>>>>
>>>>> You're going to love it.
>>>>>
>>>>> _why
>>>>> _______________________________________________
>>>>> Camping-list mailing list
>>>>> Camping-list at rubyforge.org
>>>>> http://rubyforge.org/mailman/listinfo/camping-list
>>>>
>>>> _______________________________________________
>>>> Camping-list mailing list
>>>> Camping-list at rubyforge.org
>>>> http://rubyforge.org/mailman/listinfo/camping-list
>>>
>>> _______________________________________________
>>> Camping-list mailing list
>>> Camping-list at rubyforge.org
>>> http://rubyforge.org/mailman/listinfo/camping-list
>>>
>> _______________________________________________
>> Camping-list mailing list
>> Camping-list at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/camping-list
>
> _______________________________________________
> Camping-list mailing list
> Camping-list at rubyforge.org
> http://rubyforge.org/mailman/listinfo/camping-list
>