From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH 1/2] Delete ref $frotz by moving ref file to "deleted-$frotz~ref".
Date: Tue, 17 Oct 2006 11:24:24 +0200 [thread overview]
Message-ID: <eh27f9$uog$1@sea.gmane.org> (raw)
In-Reply-To: 200610170626.25654.chriscool@tuxfamily.org
Christian Couder wrote:
>> Ref deletion is an operation that happens far far rarer than
>> updates and lookups, and I deliberately chose to optimize for
>> the latter.
>
> I think that the ref deletion usage depends on the policy of people using
> git, and there may be people that delete a ref very often.
>
> For example, when git becomes a major SCM, there may be people working on
> big projects that want to create a new branch for each new bug and then
> delete the branch when the code on the bug branch has been integrated into
> a new release and the bug is closed.
So do not pack branches then, pack only tags.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
prev parent reply other threads:[~2006-10-17 9:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-14 13:39 [PATCH 1/2] Delete ref $frotz by moving ref file to "deleted-$frotz~ref" Christian Couder
2006-10-14 18:47 ` Junio C Hamano
2006-10-17 4:26 ` Christian Couder
2006-10-17 4:41 ` Junio C Hamano
2006-10-17 5:07 ` Shawn Pearce
2006-10-17 9:24 ` Jakub Narebski [this message]
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='eh27f9$uog$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.