From: Christopher Faylor <me@cgf.cx>
To: mark@codesourcery.com, DJ Delorie <dj@redhat.com>,
nickc@redhat.com, paul@codesourcery.com,
binutils@sources.redhat.com
Subject: Re: Branches in CVS repository?
Date: Thu, 20 Jan 2005 22:54:00 -0000 [thread overview]
Message-ID: <20050120225431.GA12628@trixie.casa.cgf.cx> (raw)
In-Reply-To: <200501202238.j0KMci6B006278@greed.delorie.com>
On Thu, Jan 20, 2005 at 05:38:44PM -0500, DJ Delorie wrote:
>> I put the BRANCHES file in binutils/, since that's what Nick approved,
>> and I'm not sure who could approve putting it at top level. I'm happy
>> to move it, if necessary. If more changes need to be made, let me know.
>
>My guesses would be: Andrew for GDB, Jeff for newlib, Chris for
>cygwin. Toplevel certainly has *my* approval, for what that's worth.
>
>I just don't see how putting it in a binutils-specific place is going
>to solve the problem of coordinating branches across all the src/
>projects.
I've been following the discussion but I don't have any real preferences
one way or the other as far as cygwin is concerned. I think it's
unlikely that anyone is going to want to branch cygwin, though.
I'll chime in if I have strong objections, but I haven't had any so far.
If you don't hear from me, it's safe to assume I'm ok with the current
plan.
cgf
next prev parent reply other threads:[~2005-01-20 22:54 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
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 [this message]
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=20050120225431.GA12628@trixie.casa.cgf.cx \
--to=me@cgf.cx \
--cc=binutils@sources.redhat.com \
--cc=dj@redhat.com \
--cc=mark@codesourcery.com \
--cc=nickc@redhat.com \
--cc=paul@codesourcery.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).