On Wed, Dec 4, 2013 at 3:49 PM, Adam Spiers <aspi...@suse.com> wrote:
> Victor Lowther (victor.lowt...@gmail.com) wrote: > > On Wed, Dec 4, 2013 at 3:34 PM, Adam Spiers <aspi...@suse.com> wrote: > > > [Porting conversation from > https://github.com/crowbar/crowbar/pull/1959] > > > > > > gitify-meta breakage follows in case it's of use (BTW this was run > > > immediately after an rm -rf .releases) > > > > > > --------- 8< --------- 8< --------- 8< --------- 8< --------- 8< > --------- > > > Initialized empty Git repository in > > > /home/adam/SUSE/cloud/crowbar/git/2.0/.releases/.git/ > > > > [snip] > > > > > Adding v2.2.0-hadoop-dell to git release tracking repository > > > Switched to a new branch 'v2.2.0-hadoop-dell' > > > 2013-12-04 21:27:13 +0000: Git not setup. > > > 2013-12-04 21:27:13 +0000: Please run > > > 2013-12-04 21:27:13 +0000: git config --global user.name "your name" > > > 2013-12-04 21:27:13 +0000: git config --global user.email > "you@your.domain > > > " > > > > Well, it is rather odd that the dev tool thinks that git is not > configured > > here, and that is probably what is causing your problems. > > I don't think it's odd - it's a brand new repo, so user.email is not > set. Is your code expecting user.email to be set globally? If so, > that's a bug, because some of us use more than one email address for > git operations, and therefore cannot set user.email globally. > huh? Nothing stops you from having user.name and user.email set globally and also set per-repository -- IIRC, git will just use the most specific one. > Furthermore, if user.email is a genuine requirement in order to > proceed successfully (although I can't think why it would be), then it > should abort when it is not set, rather than simply complain and > proceed anyway. > It is because github is a super whiny whiner otherwise.
_______________________________________________ Crowbar mailing list Crowbar@dell.com https://lists.us.dell.com/mailman/listinfo/crowbar For more information: http://crowbar.github.com/
