Re: Behavior of 'git fetch' for commit hashes

2017-06-20 Thread eero.aaltonen
On 20.06.2017 01:26, Jonathan Tan wrote: > On Mon, 19 Jun 2017 10:49:36 -0700 > Jonathan Tan wrote: > >> On Mon, 19 Jun 2017 12:09:28 + >> wrote: >> >>> For version 2.13.3 > > Firstly, exactly which version of Git doesn't work? I'm assuming 2.13.1 > (as written elsewhere in your e-mail), si

Re: Behavior of 'git fetch' for commit hashes

2017-06-19 Thread Jonathan Tan
On Mon, 19 Jun 2017 10:49:36 -0700 Jonathan Tan wrote: > On Mon, 19 Jun 2017 12:09:28 + > wrote: > > > For version 2.13.3 Firstly, exactly which version of Git doesn't work? I'm assuming 2.13.1 (as written elsewhere in your e-mail), since 2.13.3 doesn't exist. > > However, the workaround

Re: Behavior of 'git fetch' for commit hashes

2017-06-19 Thread Jonathan Tan
On Mon, 19 Jun 2017 12:09:28 + wrote: > For version 2.7.4 > = > Git exits with exit code 1. > > However, if I first do 'git fetch ', then 'git fetch will > also work > > * branch-> FETCH_HEAD I suspect that what is happening is that 'git fetch ' also downloads the com

Re: Behavior of 'git fetch' for commit hashes

2017-06-19 Thread Stefan Beller
+cc Jonathan who did some work in the area. On Mon, Jun 19, 2017 at 5:09 AM, wrote: > Hello, > > I am seeing greatly different behavior for 'git fetch' commands on > version 2.7.4 and 2.13.1 when the argument to fetch is a commit hash. > > I am working on a custom Continuous Integration (CI) sys

Behavior of 'git fetch' for commit hashes

2017-06-19 Thread eero.aaltonen
Hello, I am seeing greatly different behavior for 'git fetch' commands on version 2.7.4 and 2.13.1 when the argument to fetch is a commit hash. I am working on a custom Continuous Integration (CI) system. The projects have dependencies that are simply fetched as repositories to a project subdirec