All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: Marking abandoned branches
Date: Wed, 13 Sep 2006 18:55:33 +0200	[thread overview]
Message-ID: <ee9d5j$lhd$1@sea.gmane.org> (raw)
In-Reply-To: 45083490.9020203@gmail.com

A Large Angry SCM wrote:

> Jakub Narebski wrote:
> ...
>> As it was said somewhere in this thread, you can use tags (tag objects)
for
>> that, i.e. tag each of the abandoned branches, explaining why branch wa
>> abandoned for example, remove head refs, and move tag refs to
>> refs/abandoned or refs/tags-abandoned/ or refs/Attic/ or in
refs-abandoned/
>> (the last has the advantage to not be included by default in any command,
>> even when --all is given)
> 
> Using $GIT_DIR/refs-abandoned/ means changing a number of core parts;
> think fsck and friends. Better to decide on a name in $GIT_DIR/refs/ and
> teach the various visualizers to ignore that prefix by default. Maybe
> even make the name a config item. *ducks*

Well, visualisers IIRC shows only requested branches. The only place where
abandoned branches would show even when we probably don't want would be
--all... one can try to use --all --not refs/abandoned/*

I wonder if using the "hidden" directory for abandoned branches 
(i.e. refs/.abandoned) would work...
-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git

  parent reply	other threads:[~2006-09-13 16:56 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-13 15:17 Marking abandoned branches Jon Smirl
2006-09-13 15:24 ` Petr Baudis
2006-09-13 15:31   ` Johannes Schindelin
2006-09-13 15:45     ` Jakub Narebski
2006-09-13 18:40     ` Junio C Hamano
2006-09-13 18:51       ` Jakub Narebski
2006-09-13 19:00         ` Junio C Hamano
2006-09-13 19:34           ` Jakub Narebski
2006-09-13 20:43             ` Petr Baudis
2006-09-13 20:45             ` Junio C Hamano
2006-09-13 21:02               ` Jakub Narebski
2006-09-13 21:09               ` Jakub Narebski
2006-09-13 21:32               ` Jakub Narebski
2006-09-13 15:59   ` Jon Smirl
2006-09-13 16:05     ` Johannes Schindelin
2006-09-13 17:22       ` Jon Smirl
2006-09-13 17:32         ` Shawn Pearce
2006-09-13 17:46         ` Nicolas Pitre
2006-09-13 20:31         ` Martin Langhoff
2006-09-13 20:43           ` Jakub Narebski
2006-09-13 16:09     ` Shawn Pearce
2006-09-13 16:12     ` Jakub Narebski
2006-09-13 16:40       ` A Large Angry SCM
2006-09-13 16:49         ` Shawn Pearce
2006-09-13 18:58           ` Junio C Hamano
2006-09-13 16:55         ` Jakub Narebski [this message]
2006-09-13 17:24           ` Jon Smirl
2006-09-13 17:45             ` Jakub Narebski
2006-09-14  3:37     ` Sam Vilain

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='ee9d5j$lhd$1@sea.gmane.org' \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.