public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: DJ Delorie <dj@redhat.com>
Cc: binutils@sourceware.org
Subject: Re: SVN for src (was Re: Binutils 2.18 prep)
Date: Mon, 26 Mar 2007 14:57:00 -0000	[thread overview]
Message-ID: <20070326144514.GA23900@caradoc.them.org> (raw)
In-Reply-To: <xnhcsdxnq4.fsf@greed.delorie.com>

On Thu, Mar 22, 2007 at 12:11:15PM -0400, DJ Delorie wrote:
> Daniel Jacobowitz <drow@false.org> writes:
> > You know, I think we can do this even without having to butcher the
> > layout of the repository.  Check out a directory containing just the
> > script, and have it use "svn switch -N" at the end to pick up the top
> > level files.
> 
> The thing to watch out for is an svn update to a different revision,
> which has a tendency to re-populate all the missing directories.  I've
> gotten bitten by this a few times trying to track down gcc bugs by
> date; it kept pulling in the ada/java sources and I kept trying to
> delete them.

Can you be more specific?  I tried to reproduce this, to find problems
with my tentative plan, but I couldn't.  It might be disrupted if you
use -r before and after the creation of a directory, but I think only
for that directory.

-- 
Daniel Jacobowitz
CodeSourcery

  parent reply	other threads:[~2007-03-26 14:45 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-22  2:48 Binutils 2.18 prep Daniel Jacobowitz
2007-03-22 10:06 ` SVN for src (was Re: Binutils 2.18 prep) Andrew STUBBS
2007-03-22 10:45   ` Diego 'Flameeyes' Pettenò
2007-03-22 11:06     ` Andrew STUBBS
2007-03-22 11:23       ` Diego 'Flameeyes' Pettenò
2007-03-22 14:07   ` Paul Brook
2007-03-22 14:20     ` Andrew STUBBS
2007-03-22 14:31     ` Joseph S. Myers
2007-03-22 14:11   ` Bob Rossi
2007-03-22 14:17     ` Daniel Jacobowitz
2007-03-22 15:00   ` Daniel Jacobowitz
2007-03-22 15:28     ` Daniel Jacobowitz
2007-03-22 15:51       ` Andrew STUBBS
2007-03-26 14:59         ` Daniel Jacobowitz
2007-03-26 16:32           ` Andrew STUBBS
2007-04-10 17:25             ` Daniel Jacobowitz
2007-04-11 10:22               ` Andrew STUBBS
2007-04-11 11:06                 ` Daniel Jacobowitz
2007-04-11 13:46                   ` Paul Koning
2007-04-11 14:18                 ` Ian Lance Taylor
2007-04-11 15:00                   ` Daniel Jacobowitz
2007-04-11 15:23                     ` Ian Lance Taylor
2007-03-22 15:35     ` Andrew STUBBS
2007-03-22 16:48     ` DJ Delorie
2007-03-22 17:08       ` Andrew STUBBS
2007-03-22 18:15         ` DJ Delorie
2007-03-23  9:12           ` Andrew STUBBS
2007-03-26 14:57       ` Daniel Jacobowitz [this message]
2007-03-26 15:16         ` Daniel Jacobowitz
2007-07-30 18:09 ` Binutils 2.18 prep Daniel Jacobowitz
2007-07-30 18:14   ` H.J. Lu
2007-08-01 17:57   ` Jim Wilson
2007-08-02  0:08     ` l l
2007-08-06 21:13   ` Daniel Jacobowitz
2007-08-07  8:18     ` Add bfin-*rtems* [was: Binutils 2.18 prep] Ralf Corsepius
2007-08-07  9:33       ` Nick Clifton
2007-08-09 11:45     ` Binutils 2.18 prep Matthias Klose
2007-08-13  0:33       ` 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=20070326144514.GA23900@caradoc.them.org \
    --to=drow@false.org \
    --cc=binutils@sourceware.org \
    --cc=dj@redhat.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).