Bug 698889 - Rebase git to the latest stable upstream release
Summary: Rebase git to the latest stable upstream release
Keywords:
Status: CLOSED DUPLICATE of bug 835913
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: git
Version: 6.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Adam Tkac
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-22 07:47 UTC by Adam Tkac
Modified: 2013-04-30 23:49 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-27 14:48:28 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Adam Tkac 2011-04-22 07:47:23 UTC 
Description of problem:

Current git in RHEL-6 is quite old and it makes sense to rebase it to the latest upstream bugfix release.
Comment 2 RHEL Program Management 2011-07-06 01:38:56 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
Comment 4 Suzanne Logcher 2012-01-31 21:13:19 UTC 
This request was evaluated by Red Hat Product Management for inclusion in the
current release of Red Hat Enterprise Linux. Because the affected component is
not scheduled to be updated in the current release, Red Hat is unfortunately
unable to address this request at this time.  It has been proposed for the next
release. If you would like it considered as an exception in the current
release, please ask your support representative.
Comment 5 Adam Tkac 2012-06-27 14:48:28 UTC 

*** This bug has been marked as a duplicate of bug 835913 ***
Note You need to log in before you can comment on or make changes to this bug.