Git development
 help / color / mirror / Atom feed
From: Alex Riesen <raa.lkml@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: merge-recursive: include heapq?
Date: Fri, 11 Nov 2005 19:52:46 +0100	[thread overview]
Message-ID: <20051111185246.GB13524@steel.home> (raw)
In-Reply-To: <Pine.LNX.4.63.0511111520260.7575@wbgn013.biozentrum.uni-wuerzburg.de>

Johannes Schindelin, Fri, Nov 11, 2005 15:23:04 +0100:
> I get this when pulling:
> 
> -- snip --
> Traceback (most recent call last):
>   File "./git-merge-recursive", line 4, in ?
>     from heapq import heappush, heappop
> ImportError: No module named heapq
> -- snap --
> 
> Okay, my python is *old*:
> 
> $ python -V
> Python 2.2.1
> 
> Is it worthwhile to include heapq as we did with subprocess? Or should I 
> upgrade...

Trying really trivial in-index merge...
fatal: Merge requires file-level merging
Nope.
Traceback (most recent call last):
  File "/home/raa/bin/git-merge-recursive", line 8, in ?
    from gitMergeCommon import *
  File "/home/raa/share/git-core/python/gitMergeCommon.py", line 14, in ?
    import subprocess
ImportError: No module named subprocess
Automatic merge failed/prevented; fix up by hand

That said, I thought an upgrade was worth it and upgraded my 2.3 to 2.4 :)

  reply	other threads:[~2005-11-11 18:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-11 14:23 merge-recursive: include heapq? Johannes Schindelin
2005-11-11 18:52 ` Alex Riesen [this message]
2005-11-11 19:09   ` Andrew Vasquez
2005-11-11 19:26   ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20051111185246.GB13524@steel.home \
    --to=raa.lkml@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox