This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: RFC: MI output during program execution
- From: Daniel Jacobowitz <drow at false dot org>
- To: Nick Roberts <nickrob at snap dot net dot nz>
- Cc: gdb-patches at sources dot redhat dot com
- Date: Tue, 28 Mar 2006 17:29:22 -0500
- Subject: Re: RFC: MI output during program execution
- References: <FDDE6A38-89E2-455B-BD32-08B6B75006D5@apple.com> <17160.63891.324530.937796@farnswood.snap.net.nz> <430B9BF8.500@apple.com> <17188.60739.749026.738477@farnswood.snap.net.nz> <17198.37622.443418.520082@farnswood.snap.net.nz> <17216.38283.618507.704220@kahikatea.snap.net.nz> <20051003131829.GA19106@nevyn.them.org> <17448.24343.362964.716378@kahikatea.snap.net.nz> <20060328211723.GA10392@nevyn.them.org> <17449.46536.338017.576709@kahikatea.snap.net.nz>
On Wed, Mar 29, 2006 at 10:16:40AM +1200, Nick Roberts wrote:
> > > I never created a branch in the repository but kept merging changes in the
> > > repository to my/Apple's changes.
> >
> > Unfortunately this means no one else can try what you've got...
>
> The reality is no-one will currently want to and it seemed easier to merge
> locally.
It works both ways. I'm not going to take a look at it while it's
sitting on your local drive.
> Incidentally if GDB changes version control, I think a distributed
> system like Arch would make keeping local branches easier, if thats an
> advantage. Now with CVS I have to wade through filenames starting with .#...
I think SVN is the most likely change, and SVK works fine for this - I
do that already with GCC. I want to migrate GDB, I just haven't had
time to work through the technical hurdles so I haven't started trying
to persuade folks it's a good idea.
--
Daniel Jacobowitz
CodeSourcery