This is the mail archive of the mailing list for the binutils project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Issue Tracker Used? Git migration checklist.

Exactly how many distinct projects are in the top level of the tree?

And how many of them have cross dependencies at a source level?

And in reply to the more recent one, are you suggesting that the
current binutils git repo is incomplete/broken and that a new export
will need/want to be done with a new email mapping, etc?

Thanks for pointing me at appropriate resources. Hopefully people with
detailed knowledge of what needs to be done will step up and share it
so it can be collated.



On Fri, Oct 26, 2012 at 12:19 AM, Joseph S. Myers
<> wrote:
> On Fri, 26 Oct 2012, Fred Cooke wrote:
>> What I do recall is that other projects share certain resources. Can
>> someone knowledgeable on this subject detail exactly what the
>> structure looks like, preferably with a diagram (if it's complicated
>> enough to warrant one).
> (point 6).  The basic
> principle there is to move binutils+gdb and leave it to each other project
> to decide if and when it wishes to move and what version control system to
> move to if so.
> Apart from that March / April 2011 discussion, see discussions on the gdb
> list (Oct 2011, Dec 2010, Oct 2009, Jun 2009); binutils list (Jan 2010,
> May 2009) - there may be other past discussions, and for each of those
> you'll need to check the previous / subsequent months in the archives for
> discussions crossing month boundaries.  Reading all those past discussions
> may take a while, but should allow extraction of a list of relevant issues
> for a migration plan.
> --
> Joseph S. Myers

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]