public inbox for archer@sourceware.org
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: archer@sourceware.org
Subject: Dead branches deletion?  [Re: [expr]-fix [jk-expr-committed] Fix crash on C++ DW_AT_name "".]
Date: Tue, 17 Mar 2009 21:44:00 -0000	[thread overview]
Message-ID: <20090317214352.GB15790@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <m3ab7jluc3.fsf@fleche.redhat.com>

On Tue, 17 Mar 2009 22:20:44 +0100, Tom Tromey wrote:
> (Though I see on the wiki that this is listed as a dead branch... is
> that accurate?)

Dodji suggested one can delete the remote GIT branches by:

	git push origin :branch-to-delete

(it worked for me when I was fixing up `archer-jankratochvil-fedora-merge')

Is there any reason to keep the `Dead Branches' wiki section and not just
delete those branches to make the `git branch -r | grep archer' listing
easier?  Although CVS can also delete the branches while is is usual to keep
them in the repositories.

Or maybe just delete completely empty branches (like my
archer-jankratochvil-fedora) and keep the real but obsolete ones for
historical reasons?


Thanks,
Jan

  parent reply	other threads:[~2009-03-17 21:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-15 18:29 [expr]-fix [jk-expr-committed] Fix crash on C++ DW_AT_name "" Jan Kratochvil
2009-03-17 21:21 ` Tom Tromey
2009-03-17 21:39   ` Jan Kratochvil
2009-03-17 22:00     ` Keith Seitz
2009-03-18 15:20       ` Jan Kratochvil
2009-03-17 21:44   ` Jan Kratochvil [this message]
2009-03-17 21:56     ` Dead branches deletion? [Re: [expr]-fix [jk-expr-committed] Fix crash on C++ DW_AT_name "".] Phil Muldoon

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=20090317214352.GB15790@host0.dyn.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=archer@sourceware.org \
    --cc=tromey@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).