From: Junio C Hamano <gitster@pobox•com>
To: Johannes Schindelin <Johannes.Schindelin@gmx•de>
Cc: Eric Kidd <git@randomhacks•net>, git@vger•kernel.org
Subject: Re: filter-branch: Remove original/*
Date: Sun, 15 Feb 2009 13:26:39 -0800 [thread overview]
Message-ID: <7vvdrbie7k.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <alpine.DEB.1.00.0902152046090.10279@pacific.mpi-cbg.de> (Johannes Schindelin's message of "Sun, 15 Feb 2009 20:47:19 +0100 (CET)")
Johannes Schindelin <Johannes.Schindelin@gmx•de> writes:
>> Why? Most tags will be created once and will stay there. That is how
>> tags are supposed to behave, isn't it?
>
> Exactly my point. In the common case, it does not change a thing.
Wrong.
In the common case, you will create tons of useless files that waste a
disk block to store 180-byte or so perr each tag.
> However in the case that we _do_ change tags, would you not agree that the
> reflog is _the_ place to record the change?
That merely means whoever changes the tag and wants the record of such an
update, which is uncommon, need to make sure reflog is created for that
tag (and that tag only).
next prev parent reply other threads:[~2009-02-15 21:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-14 2:45 filter-branch: Remove original/* (was Re: [RFC] What's the best UI for 'git submodule split'?) Eric Kidd
2009-02-14 21:25 ` Johannes Schindelin
2009-02-15 19:33 ` filter-branch: Remove original/* Junio C Hamano
2009-02-15 19:47 ` Johannes Schindelin
2009-02-15 21:26 ` Junio C Hamano [this message]
2009-02-15 21:33 ` Johannes Schindelin
2009-02-15 21:51 ` Junio C Hamano
2009-02-15 21:58 ` Junio C Hamano
2009-02-16 11:19 ` Johannes Schindelin
2009-02-16 11:25 ` Johannes Schindelin
2009-02-16 11:38 ` Johannes Schindelin
2009-02-16 1:19 ` Sitaram Chamarty
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=7vvdrbie7k.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox$(echo .)com \
--cc=Johannes.Schindelin@gmx$(echo .)de \
--cc=git@randomhacks$(echo .)net \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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