[email protected]
[Top] [All Lists]

Bug#512584: marked as forwarded (git.Repo.commits_between always return

Subject: Bug#512584: marked as forwarded git.Repo.commits_between always returns None
From: Debian Bug Tracking System
Date: Thu, 22 Jan 2009 00:30:06 +0000
Your message dated Thu, 22 Jan 2009 00:28:21 +0000
with message-id <[email protected]>
has caused the   report #512584,
regarding git.Repo.commits_between always returns None
to be marked as having been forwarded to the upstream software
author(s) [email protected]

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
512584: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=512584
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Subject: Debian Bug #512584: git.Repo.commits_between always returns None
From: Daniel Watkins
Date: Thu, 22 Jan 2009 00:28:21 +0000
Hello all,

Attached is an email regarding a bug in git.Repo.commits_between.  Also
attached is a patch fixing the issue.


Regards,

Dan
--- Begin Message ---
Subject: Bug#512584: git.Repo.commits_between always returns None
From: Jonny Lamb
Date: Thu, 22 Jan 2009 00:06:19 +0000
Package: python-git
Version: 0.1.5-1
Severity: normal
Tags: patch

Hi.

git.Repo.commits_between always returns None because it looks like
this:

    return Commit.find_all(self, "%s..%s" % (frm, to)).reverse()

list.reverse reverses in place and returns None.

I attach a patch to fix this.

Thanks,

-- 
Jonny Lamb, UK
[email protected]

--- End Message ---

Attachment: python-git-reverse.diff
Description: Text Data


--- End Message ---
<Prev in Thread] Current Thread [Next in Thread>
  • Bug#512584: marked as forwarded (git.Repo.commits_between always returns None), Debian Bug Tracking System <=