All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Levedahl <mlevedahl@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: [PATCH 2/3] git-bundle: die if a given ref is not included in bundle
Date: Mon, 12 Mar 2007 23:16:16 -0400	[thread overview]
Message-ID: <45F61780.2090001@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0703112302140.22628@wbgn013.biozentrum.uni-wuerzburg.de>

Johannes Schindelin wrote:
> FWIW my plans are to make the pack thin _only_ when there is only one 
> prereq and/or ref in the bundle (this prevents a _wanted_ object being 
> deltified against a not-wanted object).
>
>   
I am not sure that this is really necessary or accomplishes additional 
safety. The prerequisites must exist and be well connected in the target 
repo before the pack file is indexed: presumably, the reference objects 
all exist if the checks hold, or there is a logic flaw in the thin-pack 
generation.

If the prereq test is removed, then avoiding a thin pack might allow the 
pack file to be applied to a repo that held only the prereqs for a 
single head out of many in the bundle, but there is no info for the user 
to understand how or when to do this and I don't really think that is a 
good practice to encourage. I suggest waiting for a well defined 
use-case that really demands being able to apply only part of a pack 
file before implementing.

> Also, as mentioned above, I think that we have to check that "git rev-list 
> --objects <new-refs> --not --all" does not result in missing objects.
>   
This is certainly a good safety check: even though the prereqs are 
satisfied and all *should* be ok, some error might still exist and it is 
better to be safe.
> Ciao,
> Dscho
>   

  reply	other threads:[~2007-03-13  3:16 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-09  2:48 [PATCH 2/3] git-bundle: die if a given ref is not included in bundle Johannes Schindelin
2007-03-09  3:17 ` Mark Levedahl
2007-03-09  7:17   ` Junio C Hamano
2007-03-09 13:40     ` Mark Levedahl
2007-03-09 15:36     ` Mark Levedahl
2007-03-09 16:30       ` [PATCH] git-bundle: only die if pack would be empty, warn if ref is skipped Johannes Schindelin
2007-03-10  5:44         ` Mark Levedahl
2007-03-09 23:37       ` [PATCH 2/3] git-bundle: die if a given ref is not included in bundle Junio C Hamano
2007-03-10  5:48         ` Mark Levedahl
2007-03-10 15:39         ` Johannes Schindelin
2007-03-10 16:14           ` Mark Levedahl
2007-03-10 16:53             ` Johannes Schindelin
2007-03-10 18:30               ` Mark Levedahl
2007-03-11  1:08                 ` Johannes Schindelin
2007-03-11  1:29                   ` Junio C Hamano
2007-03-11  1:54                     ` Johannes Schindelin
2007-03-11 14:51                       ` Mark Levedahl
2007-03-11 19:58                         ` Junio C Hamano
2007-03-11 22:28                         ` Johannes Schindelin
2007-03-13  3:16                           ` Mark Levedahl [this message]
2007-03-09  3:51 ` [PATCH] git-bundle: die if the bundle is empty Mark Levedahl

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=45F61780.2090001@gmail.com \
    --to=mlevedahl@gmail.com \
    --cc=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 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.