ok, thanks. Then I'll teach JGit to fetch at least HEAD if nothing
is configured and nothing explicitly specified as refspec.
Ciao
Chris
On Sun, Nov 9, 2014 at 6:23 PM, Junio C Hamano gits...@pobox.com wrote:
Jakub Narębski jna...@gmail.com writes:
W dniu 2014-11-08 11:52, Jeff King pisze:
Christian Halstrick christian.halstr...@gmail.com writes:
ok, thanks. Then I'll teach JGit to fetch at least HEAD if nothing
is configured and nothing explicitly specified as refspec.
Sounds like a sensible thing to do to match what JGit does to what
we did from the time immemorial ;-)
Jakub Narębski jna...@gmail.com writes:
W dniu 2014-11-08 11:52, Jeff King pisze:
On Fri, Nov 07, 2014 at 04:31:08PM +0100, Christian Halstrick wrote:
In a repo where no remote.name.fetch config parameter is set what
should a git fetch do? My experiments let me think it's
HEAD:FETCH_HEAD.
On Fri, Nov 07, 2014 at 04:31:08PM +0100, Christian Halstrick wrote:
In a repo where no remote.name.fetch config parameter is set what
should a git fetch do? My experiments let me think it's
HEAD:FETCH_HEAD. Right?
Basically, yes. We always write FETCH_HEAD, regardless of the refspec.
We
W dniu 2014-11-08 11:52, Jeff King pisze:
On Fri, Nov 07, 2014 at 04:31:08PM +0100, Christian Halstrick wrote:
In a repo where no remote.name.fetch config parameter is set what
should a git fetch do? My experiments let me think it's
HEAD:FETCH_HEAD. Right?
Basically, yes. We always write
Hi,
In a repo where no remote.name.fetch config parameter is set what
should a git fetch do? My experiments let me think it's
HEAD:FETCH_HEAD. Right?
I came to this question after finding out that when I clone repos in
bare mode then they don't have and explicit remote.name.fetch in
their
6 matches
Mail list logo
