public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox•com>
To: "brian m. carlson" <sandals@crustytoothpaste•net>
Cc: Jesse Hopkins <jesse.hops@gmail•com>, git@vger•kernel.org
Subject: Re: git bundle vs git rev-list
Date: Fri, 05 Dec 2014 15:40:06 -0800	[thread overview]
Message-ID: <xmqq4mt9oecp.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20141205231350.GB223328@vauxhall.crustytoothpaste.net> (brian m. carlson's message of "Fri, 5 Dec 2014 23:13:50 +0000")

"brian m. carlson" <sandals@crustytoothpaste•net> writes:

> On Fri, Dec 05, 2014 at 03:36:18PM -0700, Jesse Hopkins wrote:
>> 1. Any thoughts on why a tag would be included by 'git bundle', when
>> 'git rev-list' with the same arguments returns empty?
>
> I think the answer to this is found in the git rev-list manpage:
>
>   List commits that are reachable by following the parent links from the
>   given commit(s), but exclude commits that are reachable from the
>   one(s) given with a ^ in front of them.
>
> The operative word here is "commits".  A bundle might include one or
> more tag objects, or unannotated tags, even though no new commits were
> available within the time frame.

Is this what a recent "git bundle create" change in 2.1.1 and 2.2
fixed?  The Release Notes to them seem to have this entry:

 * "git bundle create" with date-range specification were meant to
   exclude tags outside the range, but it did not work correctly.

  reply	other threads:[~2014-12-05 23:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-05 22:36 git bundle vs git rev-list Jesse Hopkins
2014-12-05 23:01 ` Junio C Hamano
2014-12-05 23:13 ` brian m. carlson
2014-12-05 23:40   ` Junio C Hamano [this message]
2014-12-05 23:42     ` brian m. carlson
2014-12-06  5:16 ` Jeff King

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=xmqq4mt9oecp.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox$(echo .)com \
    --cc=git@vger$(echo .)kernel.org \
    --cc=jesse.hops@gmail$(echo .)com \
    --cc=sandals@crustytoothpaste$(echo .)net \
    /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