git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Shawn Pearce <spearce@spearce.org>
Cc: git@vger.kernel.org, Jakub Narebski <jnareb@gmail.com>
Subject: Re: Marking abandoned branches
Date: Wed, 13 Sep 2006 11:58:41 -0700	[thread overview]
Message-ID: <7vfyeva90e.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20060913164937.GC29933@spearce.org> (Shawn Pearce's message of "Wed, 13 Sep 2006 12:49:37 -0400")

Shawn Pearce <spearce@spearce.org> writes:

> How about using a regex or a shell wildcard in config such as:
>
> 	[core]
> 		hideRefs = refs/abandoned/
> 		hideRefs = refs/some-garbage-i-have/

A suggestion to say "[core] anything" is out; this does _not_
belong to the core at all.

Depending on how much abandoned you want to make the abondond
refs, you can do one of the following:

 - If you just do not want visualizers to clutter what you are
   usually interested in viewing by default, teach visualizers
   to ignore that refs/ hierarchy.  Right now visualizers either
   use "ls-remote ." (e.g. gitk) or walking refs directory
   itself (e.g. gitweb) to find what refs are available.  Filter
   that and you are done.  If we were to do show-refs helper and
   if all the visualizers use it (we would need something like
   that when the refs/ work Linus is doing hits the mainline --
   walking refs directory to find available refs becomes
   officially unsupported when that happens), I am not opposed
   to give it --ignore=refs/abandoned option.  Similarly for
   ls-remote but _NOT_ peek-remote (the former is Porcelain-ish,
   the latter is core).

 - If you do not want to have even clone look at them, you need
   to have two repositories: with-clutter and main.  You call
   the current Mozilla full-import repository the former, make a
   copy of it and remove unwanted refs from it and repack.  Call
   that main and have people work on it.

   People who want to look at old, failed experiments can pull
   from with-clutter repository in two ways.  Either they can
   pull into their clone of 'main', or they make a separate
   clone using --reference option to cut the download time and
   to keep the cluttered part separate.

  reply	other threads:[~2006-09-13 18:58 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 [this message]
2006-09-13 16:55         ` Jakub Narebski
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=7vfyeva90e.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=spearce@spearce.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 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 NNTP newsgroup(s).