From: Junio C Hamano <junkio@cox.net>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Marking abandoned branches
Date: Wed, 13 Sep 2006 12:00:44 -0700 [thread overview]
Message-ID: <7vbqpja8wz.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <ee9jv6$ga0$1@sea.gmane.org> (Jakub Narebski's message of "Wed, 13 Sep 2006 20:51:36 +0200")
Jakub Narebski <jnareb@gmail.com> writes:
> Junio C Hamano wrote:
>
>> Using tag has an added benefit that you now have a place to say
>> why you dropped it. So what we would need to support this is an
>> agreed-upon name under $GIT_DIR/refs/ that is omitted from
>> display by convention across Porcelains (the core side should
>> not ignore them because even when you are abandoning them, you
>> do not want to lose them),
>
> I think that using hidden directory (dot-directory), e.g.
> $GIT_DIR/refs/.abandoned/ is a good idea... unless it conflicts somewhat
> with the way lock files are named...
Names are not interesting. Visualizers ignoring them
consistently is.
By the way, does gitweb still walk $GIT_DIR/refs hierarchy by
hand to find out the set of refs? When Linus is done with his
refs/ work, that way would become unsupported. You would need
to read from "ls-remote $GIT_DIR".
next prev parent reply other threads:[~2006-09-13 19:00 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 [this message]
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
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=7vbqpja8wz.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=jnareb@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 NNTP newsgroup(s).