On Wed, Apr 20, 2016 at 9:41 AM, Stefan Beller wrote:
> On Wed, Mar 2, 2016 at 12:49 AM, Jeff King wrote:
>> On Tue, Mar 01, 2016 at 07:17:20PM -0400, Joey Hess wrote:
>>
>>> Junio C Hamano wrote:
>>> > A more pertinent question may be which version of Git did
On Wed, Mar 2, 2016 at 12:49 AM, Jeff King wrote:
> On Tue, Mar 01, 2016 at 07:17:20PM -0400, Joey Hess wrote:
>
>> Junio C Hamano wrote:
>> > A more pertinent question may be which version of Git did the above
>> > ever work, I guess. We fairly liberally chdir around and I do not
I'll add Jens, who has deep knowledge of submodules.
On Wed, Mar 2, 2016 at 8:52 AM, Joey Hess wrote:
> joey@darkstar:/tmp/empty>git init sub1
> Initialized empty Git repository in /tmp/empty/sub1/.git/
> joey@darkstar:/tmp/empty>git init sub2
> Initialized empty Git repository
joey@darkstar:/tmp/empty>git init sub1
Initialized empty Git repository in /tmp/empty/sub1/.git/
joey@darkstar:/tmp/empty>git init sub2
Initialized empty Git repository in /tmp/empty/sub2/.git/
joey@darkstar:/tmp/empty>cd sub1
joey@darkstar:/tmp/empty/sub1>date > f1 ; git add f1; git commit -m add
On Tue, Mar 01, 2016 at 07:17:20PM -0400, Joey Hess wrote:
> Junio C Hamano wrote:
> > A more pertinent question may be which version of Git did the above
> > ever work, I guess. We fairly liberally chdir around and I do not
> > think we deliberately avoid assuming that "cd .git && cd .." might
Junio C Hamano wrote:
> A more pertinent question may be which version of Git did the above
> ever work, I guess. We fairly liberally chdir around and I do not
> think we deliberately avoid assuming that "cd .git && cd .." might
> not come back to the original directory, for example, so I
Stefan Beller wrote:
> To elaborate on that: Starting in 2.7 parts of the submodule stuff
> has been rewritten in C, in 2.8 even more and there is more in flight for
> > 2.8.
>
> However your bug is also to be found in 2.6, which doesn't contain any
> recent rewrites, so it is a rather long
Stefan Beller writes:
> On Tue, Mar 1, 2016 at 12:42 PM, Joey Hess wrote:
>> git init gitdir
>> mkdir worktree
>> cd worktree
>> ln -s ../gitdir/.git .git
>> git submodule add /any/git/repo sub
>>
>> fatal:
On Tue, Mar 1, 2016 at 1:39 PM, Stefan Beller wrote:
> On Tue, Mar 1, 2016 at 12:42 PM, Joey Hess wrote:
>> git init gitdir
>> mkdir worktree
>> cd worktree
>> ln -s ../gitdir/.git .git
>> git submodule add
On Tue, Mar 1, 2016 at 12:42 PM, Joey Hess wrote:
> git init gitdir
> mkdir worktree
> cd worktree
> ln -s ../gitdir/.git .git
> git submodule add /any/git/repo sub
>
> fatal: Could not chdir to '../../../sub': No such file or
git init gitdir
mkdir worktree
cd worktree
ln -s ../gitdir/.git .git
git submodule add /any/git/repo sub
fatal: Could not chdir to '../../../sub': No such file or directory
Fairly sure this is a bug..
--
see shy jo
signature.asc
Description:
On Tue, Mar 10, 2015 at 09:56:42PM +1300, Jens Lehmann wrote:
Config like this is in a funny boat. We do not want it to cross
transport boundaries, so that if we run:
git -c foo=bar clone /some/local/path
the process serving /some/local/path should not see the foo option[1].
But for
Am 09.03.2015 um 20:43 schrieb Jeff King:
On Thu, Mar 05, 2015 at 04:20:10PM +0100, Aschemann Gerd wrote:
seems to be a bug: If adding a submodule from an https URL with a certificate
issued by StartSSL (or even a private/self-signed one?) leads to the following
error:
$ git -c
On Thu, Mar 05, 2015 at 04:20:10PM +0100, Aschemann Gerd wrote:
seems to be a bug: If adding a submodule from an https URL with a certificate
issued by StartSSL (or even a private/self-signed one?) leads to the
following error:
$ git -c http.sslverify=false submodule add
Hi,
seems to be a bug: If adding a submodule from an https URL with a certificate
issued by StartSSL (or even a private/self-signed one?) leads to the following
error:
$ git -c http.sslverify=false submodule add https://example.com/git/xxx.git
Cloning into 'xxx'...
fatal: unable to
Am 26.09.2012 06:18, schrieb Jonathan Johnson:
I believe I have found an issue with the way `submodule add` detects a
submodule that already exists in the repository.
Yes, this is an issue and thanks for the detailed report.
To reproduce
1) add a git submodule in a specific location
I believe I have found an issue with the way `submodule add` detects a
submodule that already exists in the repository.
To reproduce
1) add a git submodule in a specific location (we'll say it's at
`./submodule/location`)
2) go through the normal steps of removing a submodule, as listed here
17 matches
Mail list logo