On Fri, Dec 05, 2014 at 03:36:18PM -0700, Jesse Hopkins wrote:
> #Create the bundle
> git bundle create out.bundle --all "--since="
Others pointed out that a bug in the handling of --since may be the
culprit here. However, I'd encourage you to use actual sha1s, as they
are going to be more robust
On Fri, Dec 05, 2014 at 03:40:06PM -0800, Junio C Hamano wrote:
> "brian m. carlson" 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?
>
"brian m. carlson" 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:
>
> L
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 follo
Jesse Hopkins writes:
> 2. Is there a way to list commits contained in the bundle file itself?
> This seems like it would be more robust than trying to re-create the
> commit list via 'git rev-list'.
"git bundle list-heads o.bndl" shows the positive endpoints, but
there is no corresponding "git
Hello all –
I am working to create a wrapper around git bundle to synchronize of
git repos via sneakernet from network ‘a’ to network ‘b’ transfer on a
fairly frequent basis (daily to weekly). Network ‘b’ has a
gatekeeper who is persnickety about what content might end up on his
network. The
6 matches
Mail list logo
