On 3/20/10, Junio C Hamano <gitster@xxxxxxxxx> wrote: > Alex Riesen <raa.lkml@xxxxxxxxx> writes: > > > The values passed this way will override whatever is defined > > in the config files. > > > > Signed-off-by: Alex Riesen <raa.lkml@xxxxxxxxx> > > --- > > > > Someone wanted to have this once. I accidentally remembered > > that when I wanted to temporarily set some config parameter > > (format.suffix?). From looking at code it seemed simple enough, > > so I did it. > > > How does this interact with core.worktree and the setup sequence in > general? To me it looks like another config file to the config stack. No thing can go worse (except that if you have core.worktree in $GIT_DIR/config, now also specify -c core.worktree=foo, then core.worktree code would be called twice). However, specifying "-c foo=relativepath" may surprise users. Current working directory may have been moved when that config is used. -- Duy -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html