On Fri, Dec 05, 2014 at 03:40:06PM -0800, Junio C Hamano wrote: > "brian m. carlson" <sandals@xxxxxxxxxxxxxxxxxxxx> 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. That certainly could be the case. I was thinking that perhaps someone had created a tag recently, but your explanation is more likely. -- brian m. carlson / brian with sandals: Houston, Texas, US +1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187
Attachment:
signature.asc
Description: Digital signature