Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Jim Meyering <jim@meyering.net>
Cc: gdb@sourceware.org
Subject: Re: gdb.git hiccup
Date: Sat, 03 Oct 2009 17:05:00 -0000	[thread overview]
Message-ID: <20091003170531.GA32086@adacore.com> (raw)
In-Reply-To: <87k4zclc87.fsf@meyering.net>

Hi Jim,

Bad luck on the gdb.git repository. I have been very much enjoying
the git mirror for GDB, so I'm very thankful you're taking the time
to do that for us.

> If anyone can say which tags and branches can be removed, I'll be happy
> to remove them and prune all associated commits.

Do you think they take much space? Perhaps keeping all the branches
related to GDB might be convenient occasionally.

The following branches are not gdb-related, so I'm assuming we can
get rid of them:

  origin/binutils-2_10-branch
  origin/binutils-2_11-branch
  origin/binutils-2_12-branch
  origin/binutils-2_13-branch
  origin/binutils-2_14-branch
  origin/binutils-2_15-branch
  origin/binutils-2_16-branch
  origin/binutils-2_17-branch
  origin/binutils-2_18-branch
  origin/binutils-2_19-branch
  origin/binutils-2_20-branch
  origin/binutils-arc-20081103-branch
  origin/binutils-csl-2_17-branch
  origin/binutils-csl-arm-2005q1-branch
  origin/binutils-csl-gxxpro-3_4-branch
  origin/cgen-1_1-branch
  origin/cgf-deleteme
  origin/cgf-dev-branch

Not sure what this is about, but they don't follow the naming convention
for GDB branches, so I think it's OK to delete these as well:

  origin/cr-0x5e6
  origin/cr-0x5ef
  origin/cr-0x5f1
  origin/cr-0x9b
  origin/cr-0x9c
  origin/cr-0x9e

These are really old development branches. I don't think anyone
is gonig to refer to them anymore, so I think it's OK to delete these:

  origin/cagney-unwind-20030108-branch
  origin/cagney_bfdfile-20040213-branch
  origin/cagney_bigcore-20040122-branch
  origin/cagney_convert-20030606-branch
  origin/cagney_fileio-20030521-branch
  origin/cagney_frameaddr-20030403-branch
  origin/cagney_framebase-20030326-branch
  origin/cagney_lazyid-20030317-branch
  origin/cagney_offbyone-20030303-branch
  origin/cagney_regbuf-20020515-branch
  origin/cagney_sysregs-20020825-branch
  origin/cagney_tramp-20040309-branch
  origin/cagney_writestrings-20030508-branch
  origin/cagney_x86i386-20030821-branch
  origin/carlton_dictionary-branch
  origin/kettenis-i386newframe-20030308-branch
  origin/kettenis_i386newframe-20030406-branch
  origin/kettenis_i386newframe-20030419-branch
  origin/kettenis_sparc-20030918-branch
  origin/kseitz_interps-20020528-branch
  origin/offbyone-20030313-branch
  origin/sid-20020905-branch
  origin/tcltk840-20020924-branch

I noticed the same branch/tags are sometimes duplicated, one under
origin and the other under origin/cvs.  Not sure if one of the two
needs to go.

Hope this helps,
-- 
Joel


  reply	other threads:[~2009-10-03 17:05 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-03 12:30 Jim Meyering
2009-10-03 13:22 ` Jim Meyering
2009-10-03 15:38   ` Jim Meyering
2009-10-03 17:05     ` Joel Brobecker [this message]
2009-10-03 23:35     ` Daniel Jacobowitz
2009-10-04  6:51       ` Jim Meyering
2009-10-04 11:09         ` Frank Ch. Eigler
2009-10-04 12:15           ` Matt Rice
2009-10-04 12:43             ` Jim Meyering
     [not found]               ` <20091004142139.GA19501@host0.dyn.jankratochvil.net>
2009-10-04 20:16                 ` Jim Meyering
2009-10-05  1:46                   ` Jan Kratochvil
2009-10-05 10:14                 ` Jim Meyering
2009-10-06 20:48                   ` Jan Kratochvil
2009-10-06 21:12                     ` Jim Meyering
2009-10-06 21:23                     ` Jim Meyering
2009-10-04 12:15           ` Jim Meyering
2009-10-04 12:40             ` Frank Ch. Eigler
2009-10-04 14:49         ` Christopher Faylor
2009-10-04 15:05           ` Jim Meyering
2009-10-04 15:15             ` Christopher Faylor
2009-10-04 20:34               ` Jim Meyering
2009-10-06 22:03     ` Joel Brobecker
2009-10-07 14:52       ` Jim Meyering
     [not found]         ` <20091007192519.GK16338@adacore.com>
2009-10-07 21:13           ` Jim Meyering
2009-10-08  9:20           ` Jim Meyering

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=20091003170531.GA32086@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb@sourceware.org \
    --cc=jim@meyering.net \
    /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