On Mon, 17 Feb 2014 08:58:54 +0100
bryan rasmussen <rasmussen.br...@gmail.com> wrote:
> >I'm also curious what's the real use case for this tool. After
> >skimming through the description only pair (hot-seat?) programming
> >seems like a good fit, otherwise one just does
> > $ git add --local user.name ...
> > $ git add --local user.email ...
> wouldn't it also be useful for switching if you use one profile when
> working for company X and another one for company Y and so forth?
> I guess if you were doing a whole day for company Y you would just
> switch normally, but if you needed to just put in a quick bug fix?
> Would this also apply if you had different profiles for different git
"--local" sets the designated option in a local repository to which the
command is applied. I have no mental power to imagine a situation --
other than the hot-seat style of collaborative working discussed
above -- which would require the developer to change identities when
recording different commits in the same repository. I cannot imagine
working on the same local repository for more than one company at the
same time. For sure, we might imagine any number of fabulous situations
which would require such identity switching, including the developer
being held captive and forced to do that by little green men from Alpha
Centauri or whispers in the developer's head, but during the normal
workflow? I personally doubt it.
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/groups/opt_out.