Jens Lehmann writes:
> Not inside the submodule, me thinks they only make sense in the
> superproject (that's why we clean the environment before working
> inside the submodule).
Yes, that is fundamental and the only sane behaviour that comes from
what submodules are. They are free-standing pro
Am 23.07.2012 22:34, schrieb Junio C Hamano:
> Jens Lehmann writes:
>
>> We could get rid of the core.worktree setting by assuming that the
>> directory a gitfile was found in is the root of the repo's work
>> tree (unless configured otherwise).
>
> Now you lost me. If you have .git that is not
Jens Lehmann writes:
> We could get rid of the core.worktree setting by assuming that the
> directory a gitfile was found in is the root of the repo's work
> tree (unless configured otherwise).
Now you lost me. If you have .git that is not a directory but is a
gitfile, then you do not need GIT_
Am 23.07.2012 20:21, schrieb Junio C Hamano:
> Jens Lehmann writes:
>
>> Am 23.07.2012 07:09, schrieb Junio C Hamano:
>>> Daniel Graña writes:
>>>
A common way to track dotfiles with git is using GIT_DIR and
GIT_WORK_TREE to move repository out of ~/.git with something like:
PPS: Yes, I know that I am replying in a patch thread. I will try it asap.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Mon, Jul 23, 2012 at 7:09 AM, Junio C Hamano wrote:
> I think this is in line with what we discussed earlier on list when
> the interaction between GIT_DIR/GIT_WORK_TREE and submodules came up
> the last time. Jens?
Yes, it is.
I still have your email marked as TODO to get back to you as I
On Mon, Jul 23, 2012 at 2:38 PM, Jens Lehmann wrote:
> Am 23.07.2012 07:09, schrieb Junio C Hamano:
>> Daniel Graña writes:
>>
>>> A common way to track dotfiles with git is using GIT_DIR and
>>> GIT_WORK_TREE to move repository out of ~/.git with something like:
>>>
>>> git init --bare ~/.do
Jens Lehmann writes:
> Am 23.07.2012 07:09, schrieb Junio C Hamano:
>> Daniel Graña writes:
>>
>>> A common way to track dotfiles with git is using GIT_DIR and
>>> GIT_WORK_TREE to move repository out of ~/.git with something like:
>>>
>>> git init --bare ~/.dotfiles
>>> alias dotfiles=
Am 23.07.2012 07:09, schrieb Junio C Hamano:
> Daniel Graña writes:
>
>> A common way to track dotfiles with git is using GIT_DIR and
>> GIT_WORK_TREE to move repository out of ~/.git with something like:
>>
>> git init --bare ~/.dotfiles
>> alias dotfiles="GIT_DIR=~/.dotfiles GIT_WORK_TR
Daniel Graña writes:
> A common way to track dotfiles with git is using GIT_DIR and
> GIT_WORK_TREE to move repository out of ~/.git with something like:
>
> git init --bare ~/.dotfiles
> alias dotfiles="GIT_DIR=~/.dotfiles GIT_WORK_TREE=~ git"
>
> dotfiles add ~/.bashrc
> dotfile
A common way to track dotfiles with git is using GIT_DIR and
GIT_WORK_TREE to move repository out of ~/.git with something like:
git init --bare ~/.dotfiles
alias dotfiles="GIT_DIR=~/.dotfiles GIT_WORK_TREE=~ git"
dotfiles add ~/.bashrc
dotfiles commit -a -m "add my bashrc"
..
11 matches
Mail list logo