From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 0/2] Controversial blob munging series
Date: Mon, 23 Apr 2007 20:49:46 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0704232047480.8822@racer.site> (raw)
In-Reply-To: <7virbnexuc.fsf@assigned-by-dhcp.cox.net>
Hi,
On Mon, 23 Apr 2007, Junio C Hamano wrote:
> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>
> > On Mon, 23 Apr 2007, Junio C Hamano wrote:
> > ...
> >> ... I am inclined to think that this is quite fundamental. I
> >> think you just fell into category who want "extended semantics"
> >> Linus talked about in $gmane/45214:
> >>
> >> I suspect that this gets some complaining off our back, but I *also*
> >> suspect that people will actually end up really screwing themselves with
> >> something like this and then blaming us and causing a huge pain down the
> >> line when we've supported this and people want "extended semantics" that
> >> are no longer clean.
> >>
> >> which is kind of dissapointing.
>
> I think this was the biggest worry. If even Dscho, who is among
> a dozen people with the most intimate knowledge of git on the
> planet, gets it wrong, I can almost guarantee that we will get
> into the mess Linus predicted above.
Flattering always works :-)
> >> Even if you somehow solved the issue of "stat" rule, I do not
> >> know what your plans are to manage the blobs that you drop in
> >> the object store. The list of object names in the mail-index
> >> file you are generating do not count as connectivity for the
> >> purpose of fetch/push/fsck/prune.
> >
> > I had the idea to update a ref, which holds "trees" of message-id -> blob
> > pairs, and get updated at the same time.
>
> I somehow thought this mailbox thing was because you wanted to
> transfer mailboxes across repositories. How would you prevent
> that ref from getting out of sync with the mail-index file git
> knows nothing about its involvement in connectivity?
If your suspicion was that I did not really think it through, then you're
correct. Of course, I would have transferred _all_ refs anyway, since the
whole point of the exercise is to lose nothing.
However, I see where your argument is going.
Since Julian pointed out that there is a maildir patch for pine, I'll
probably go for that one, since it is hanging lower.
Ciao,
Dscho
prev parent reply other threads:[~2007-04-23 18:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-22 6:08 [PATCH 0/2] Controversial blob munging series Junio C Hamano
2007-04-22 6:08 ` [PATCH 1/2] Add 'filter' attribute and external filter driver definition Junio C Hamano
2007-04-22 6:08 ` [PATCH 2/2] Add 'ident' conversion Junio C Hamano
2007-04-23 13:50 ` [PATCH 0/2] Controversial blob munging series Johannes Schindelin
2007-04-23 16:29 ` Julian Phillips
2007-04-23 16:54 ` Johannes Schindelin
2007-04-23 17:13 ` Junio C Hamano
2007-04-23 17:35 ` Johannes Schindelin
2007-04-23 18:42 ` Junio C Hamano
2007-04-23 18:49 ` Johannes Schindelin [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=Pine.LNX.4.64.0704232047480.8822@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).