From: Mark Levedahl <mlevedahl@gmail.com>
To: Junio C Hamano <junkio@cox.net>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>, git@vger.kernel.org
Subject: Re: [PATCH 2/3] git-bundle: die if a given ref is not included in bundle
Date: Sat, 10 Mar 2007 00:48:20 -0500 [thread overview]
Message-ID: <45F246A4.2040304@gmail.com> (raw)
In-Reply-To: <7v1wjy56qf.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> My answer is that it should list master and side as the
> available heads and master itself as also a prerequisite (which
> is not what the current code does).
>
So, practically speaking the proposal is that for each ref where
git-bundle currently issues a warning, instead the ref should be added
to the prerequisites list, and that all refs given on the command line
are in the bundle's defined refs.
Sounds reasonable to me.
Mark
next prev parent reply other threads:[~2007-03-10 5:48 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 [this message]
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
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=45F246A4.2040304@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 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).