Thanks for the feedback Guys. The main use cases for Gitsu are for pairing,
switching the user for different projects, and having multiple developers
on the same machine. In the first and last case (multiple users on the same
machine), Gitsu helps you switch the global user easily, and works with
multiple users at once for pairing. As Konstantin points out, the second
case (different credentials per project) can be addressed by updating the
config manually. The win with Gitsu here is being able to use "git su me"
instead of "git config user.name me && git config user.email m...@example.com".
This is of benefit if you need to do this on multiple projects on an
On 17 February 2014 20:53, bryan rasmussen <rasmussen.br...@gmail.com>wrote:
> Ok thanks, I wasn't thinking it through there since I always use
> global, so not used to using the local setting as part of my workflow.
> >>I cannot imagine
> >working on the same local repository for more than one company at the
> >same time.
> I guess I could, in little green man fashion though.
> On Mon, Feb 17, 2014 at 10:22 AM, Konstantin Khomoutov
> <flatw...@users.sourceforge.net> wrote:
> > 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
> >> services?
> > "--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 a topic in the
> Google Groups "Git for human beings" group.
> To unsubscribe from this topic, visit
> To unsubscribe from this group and all its topics, send an email to
> For more options, visit https://groups.google.com/groups/opt_out.
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.