On Fri, Mar 8, 2013 at 12:26 PM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> When pushing from work do you push to non-work repositories using your work
> key?
>
no.
>
>
When pushing from work do you push to non-work repositories using your work
key?
On 8 March 2013 17:15, Benson Margulies wrote:
> As always, explaining the actual problem I'm trying to solve may help.
>
> I need to maintain two identities on github: one for work, and one for
> not-so-work. So,
As always, explaining the actual problem I'm trying to solve may help.
I need to maintain two identities on github: one for work, and one for
not-so-work. So, I have two ssh key pairs.
Using git from command line, I address this with an option to git when I
clone:
git clone --config ssh.key=/u
Please check GitCheckoutCommand[1]
Robert
[1]
http://maven.apache.org/scm/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/xref/org/apache/maven/scm/provider/git/gitexe/command/checkout/GitCheckOutCommand.html
Op Fri, 08 Mar 2013 14:33:16 +0100 schreef Brett Porter :
On 08/03/2013, at 11:59 PM, Benson Margulies wrote:
> I'd like to add some 'clone' options for use with git in
> release:perform that could live in settings.xml.
I'm curious - how would clone options look in settings.xml? Aside from
properties, or perhaps server credentials - most other things
I'd like to add some 'clone' options for use with git in
release:perform that could live in settings.xml. I'm not even sure how
many JIRAs I need. Is this something that gets done in the scm plugin
and then cross-wired to the release plugin?
