git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: filter-branch: Remove original/*

From
Sitaram Chamarty <sitaramc@gmail.com>
Date
Feb 16, 2009, 01:19 UTC
Message-ID
<slrngphfok.hul.sitaramc@sitaramc.homelinux.net>
In-Reply-To
<7vvdrbie7k.fsf@gitster.siamese.dyndns.org>
On 2009-02-15, Junio C Hamano <gitster@pobox.com> wrote:
Show 11 quoted lines
> 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.

Instead of a separate file for each tag, why not something like logs/TAGS, which just records tag creations.

The downside is it wouldn't represent a *continuous state* of anything in particular, because you can create tags for any commit while on any (other) branch. I'm not smart enough to figure out the implications of that across the entire system.

Previous: Johannes Schindelin
Message 12 of 12 in “filter-branch: Remove original/* (was Re: [RFC] What's the best UI for 'git submodule split'?)”
  1. Eric KiddFeb 14, 2009
  2. Johannes SchindelinFeb 14, 2009
  3. Junio C HamanoFeb 15, 2009
  4. Johannes SchindelinFeb 15, 2009
  5. Junio C HamanoFeb 15, 2009
  6. Johannes SchindelinFeb 15, 2009
  7. Junio C HamanoFeb 15, 2009
  8. Junio C HamanoFeb 15, 2009
  9. Johannes SchindelinFeb 16, 2009
  10. Johannes SchindelinFeb 16, 2009
  11. Johannes SchindelinFeb 16, 2009
  12. Sitaram ChamartyFeb 16, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.