SCIENTIFIC-LINUX-USERS Archives

June 2014

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Patrick J. LoPresti" <[log in to unmask]>
Reply To:
Patrick J. LoPresti
Date:
Wed, 18 Jun 2014 17:22:58 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (18 lines)
(different topic, different reply)

On Wed, Jun 18, 2014 at 1:16 PM, Lamar Owen <[log in to unmask]> wrote:
> The various spec files include the release numbers, and you can track
> the spec files with their commit IDs.

Could you be more specific? In particular, is there a reliable,
automated procedure to obtain a git checkout of the exact source code
for a particular complete RHEL release, and also for each subsequent
update?

I am not concerned about anybody tampering with the git repo. I am
concerned about how hard it is for third parties to create derivatives
of Red Hat. (Note "derivatives of Red Hat", not "derivatives of
CentOS".)

 - Pat

ATOM RSS1 RSS2