Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Prevent source file errors in --batch-silent mode
Date: Sat, 03 May 2008 20:54:00 -0000	[thread overview]
Message-ID: <1209846868.7034.96.camel@localhost.localdomain> (raw)
In-Reply-To: <20080503142635.GA17718@caradoc.them.org>

On Sat, 2008-05-03 at 10:26 -0400, Daniel Jacobowitz wrote:
> On Sat, May 03, 2008 at 01:47:26AM -0300, Thiago Jung Bauermann wrote:
> > > and "switch src to svn 1.5 when it is released", FWIW.
> > 
> > Hum... any reason in particular for that? It seems everyone keeps their
> > own version of the GDB source tree. Using a distributed VCS would ease
> > that work and benefit everybody...
> 
> Because SVN is similar enough to CVS to be an easy transition and

When you say easy are you thinking of the similar concepts and usability
they have, or the migration process in itself?

> advanced enough that it can gateway to and from other VCS's (svk, git,
> presumably hg too) reliably for those who prefer something different.

I just read the git-svn manpage and there are some restrictions you
should observe to avoid problems. I never used the tool, but it seems
those restrictions can become annoying, so if the svn route is to be
taken I think having the read-only git mirror cgf mentions would be a
useful thing.

> There's no need to break up everyone's workflow and I refuse to do it.

By this you mean forcing everyone to grok/use the distributed model? If
this is an important consideration, Bazaar can be a good option since it
supports both workflows at the same time in a given repo, i.e., a
developer can choose to do a checkout or a clone.
-- 
[]'s
Thiago Jung Bauermann
Software Engineer
IBM Linux Technology Center


  reply	other threads:[~2008-05-03 20:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-21 19:34 Andrew STUBBS
2008-04-28 19:02 ` Andrew STUBBS
2008-05-01 20:34 ` Daniel Jacobowitz
2008-05-02 11:35   ` Andrew STUBBS
2008-05-02 13:46     ` Daniel Jacobowitz
2008-05-02 14:03       ` Andrew STUBBS
2008-05-02 14:10         ` Daniel Jacobowitz
2008-05-03  6:23           ` Thiago Jung Bauermann
2008-05-03 14:26             ` Christopher Faylor
2008-05-03 20:56               ` Thiago Jung Bauermann
2008-05-03 15:33             ` Daniel Jacobowitz
2008-05-03 20:54               ` Thiago Jung Bauermann [this message]
2008-05-03 21:48                 ` Daniel Jacobowitz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1209846868.7034.96.camel@localhost.localdomain \
    --to=bauerman@br.ibm.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox