From: Andrew Pinski <pinskia@gmail.com>
To: Jason Merrill <jason@redhat.com>
Cc: Paolo Bonzini <bonzini@gnu.org>,
"Joseph S. Myers" <joseph@codesourcery.com>,
Richard Guenther <richard.guenther@gmail.com>,
gdr@integrable-solutions.net, gcc@gcc.gnu.org
Subject: Re: delete dead feature branches?
Date: Mon, 12 Oct 2009 21:21:00 -0000 [thread overview]
Message-ID: <de8d50360910121417v3eb14c69ue4a4899acac23320@mail.gmail.com> (raw)
In-Reply-To: <4AD39C64.3020304@redhat.com>
On Mon, Oct 12, 2009 at 2:15 PM, Jason Merrill <jason@redhat.com> wrote:
> On 10/12/2009 10:22 AM, Paolo Bonzini wrote:
>>
>> Yep. Anyone deleting dead branches should add a link to the last "live"
>> version in branches.html. It seems easier to me to move them under
>> branches/dead, and possibly create branches/merged.
>
> Multiple directory levels under branches/ confuse git-svn; it thinks "dead"
> is a single branch. I'd rather not expand on that usage.
That seems like a huge bug in git-svn because we already use multiple
directory levels under branches. Hint ibm and redhat and debain.
Thanks,
Andrew Pinski
next prev parent reply other threads:[~2009-10-12 21:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-25 15:28 Jason Merrill
2009-09-25 15:48 ` Ian Lance Taylor
2009-09-25 18:42 ` Joseph S. Myers
2009-09-25 19:00 ` Jason Merrill
2009-09-25 19:21 ` Gabriel Dos Reis
2009-09-25 19:24 ` Richard Guenther
2009-09-25 23:45 ` Joseph S. Myers
2009-09-26 4:54 ` Source control features (Was: Re: delete dead feature branches?) Joern Rennecke
2009-10-12 14:24 ` delete dead feature branches? Paolo Bonzini
2009-10-12 21:17 ` Jason Merrill
2009-10-12 21:21 ` Andrew Pinski [this message]
2009-10-12 22:18 ` Jason Merrill
2009-10-14 2:06 ` Daniel Berlin
2009-10-14 3:16 ` Joern Rennecke
2009-10-14 6:33 ` Alexandre Oliva
2009-10-13 1:19 ` Michael Matz
2009-10-13 13:50 ` Jason Merrill
2009-10-14 1:37 ` Ben Elliston
2009-10-14 5:55 ` Jason Merrill
2009-10-14 9:36 ` Michael Matz
2009-10-15 8:17 ` Ben Elliston
2009-10-25 18:32 ` Gerald Pfeifer
2009-10-11 22:51 ` 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=de8d50360910121417v3eb14c69ue4a4899acac23320@mail.gmail.com \
--to=pinskia@gmail.com \
--cc=bonzini@gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=gdr@integrable-solutions.net \
--cc=jason@redhat.com \
--cc=joseph@codesourcery.com \
--cc=richard.guenther@gmail.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).