From: Mark Mitchell <mark@codesourcery.com>
To: Andreas Schwab <schwab@suse.de>
Cc: Nick Clifton <nickc@redhat.com>, Ian Lance Taylor <ian@airs.com>,
libc-alpha@sources.redhat.com, binutils@sources.redhat.com
Subject: Re: Branches in CVS repository?
Date: Mon, 17 Jan 2005 16:55:00 -0000 [thread overview]
Message-ID: <41EBEE05.8000105@codesourcery.com> (raw)
In-Reply-To: <jeekgkyp3r.fsf@sykes.suse.de>
Andreas Schwab wrote:
> Mark Mitchell <mark@codesourcery.com> writes:
>
>
>>In thinking about this a bit further, I realize that the issue is
>>complicated by the fact that binutils is part of the whole src/
>>repository. A branch created just in the binutils portion might be
>>confusing, and, in any case, doing something like a new assembler port
>>requires changes to other parts of the tree as well to support new opcodes
>>and such.
>
>
> You only need to check out the binutils module.
Yes, but it contains code from other subdirectories. For example, it
contains all the files in the top level directory, the stuff in intl/,
the stuff in libiberty/, and the stuff in opcodes/. A branch made in
the tree I checked out for binutils will create branches in all of these
places. So, we need to get agreement that it's OK to create branches in
those directories as well.
--
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com
(916) 791-8304
next prev parent reply other threads:[~2005-01-17 16:55 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-15 0:03 Mark Mitchell
2005-01-15 2:12 ` Ian Lance Taylor
2005-01-17 10:33 ` Nick Clifton
2005-01-17 16:42 ` Mark Mitchell
2005-01-17 16:53 ` Andreas Schwab
2005-01-17 16:55 ` Mark Mitchell [this message]
2005-01-17 17:02 ` DJ Delorie
2005-01-17 17:11 ` Andreas Schwab
2005-01-17 17:17 ` Mark Mitchell
2005-01-17 17:43 ` DJ Delorie
2005-01-17 17:51 ` Mark Mitchell
2005-01-18 9:36 ` Nick Clifton
2005-01-19 5:52 ` Mark Mitchell
2005-01-19 9:58 ` Nick Clifton
2005-01-19 15:49 ` Mark Mitchell
2005-01-19 16:02 ` Nick Clifton
2005-01-19 16:23 ` Dave Korn
2005-01-19 16:26 ` Mark Mitchell
2005-01-19 16:34 ` Nick Clifton
2005-01-19 17:50 ` Mark Mitchell
2005-01-19 18:10 ` Richard Earnshaw
2005-01-19 18:12 ` Mark Mitchell
2005-01-19 18:16 ` Paul Brook
2005-01-19 18:19 ` Mark Mitchell
2005-01-20 22:06 ` Mark Mitchell
2005-01-20 22:31 ` Eric Botcazou
2005-01-21 3:15 ` Mark Mitchell
2005-01-20 22:38 ` DJ Delorie
2005-01-20 22:54 ` Christopher Faylor
2005-01-21 9:49 ` Nick Clifton
2005-01-21 13:27 ` DJ Delorie
2005-01-21 13:35 ` DJ Delorie
2005-01-22 9:28 ` Nick Clifton
2005-01-23 19:01 ` Mark Mitchell
2005-01-23 19:50 ` DJ Delorie
2005-01-25 16:38 ` Andrew Cagney
2005-01-20 11:58 ` Nick Clifton
2005-01-20 17:26 ` DJ Delorie
2005-01-19 20:28 ` Andrew Cagney
2005-01-20 10:46 ` Richard Earnshaw
2005-01-20 17:39 ` Andrew Cagney
2005-01-20 18:18 ` Ian Lance Taylor
2005-01-23 13:18 ` Thorsten Glaser
2005-01-19 10:06 ` Richard Earnshaw
2005-01-19 11:32 ` Nick Clifton
2005-01-17 17:40 ` DJ Delorie
2005-01-17 17:43 ` Andreas Schwab
2005-01-17 17:50 ` DJ Delorie
2005-01-17 17:57 ` Dave Korn
2005-01-17 23:58 ` Ben Elliston
2005-01-18 2:21 ` DJ Delorie
2005-01-18 6:02 ` Ben Elliston
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=41EBEE05.8000105@codesourcery.com \
--to=mark@codesourcery.com \
--cc=binutils@sources.redhat.com \
--cc=ian@airs.com \
--cc=libc-alpha@sources.redhat.com \
--cc=nickc@redhat.com \
--cc=schwab@suse.de \
/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).