Received: by 10.100.76.4 with SMTP id y4mr6304582ana.21.1336400650250;
        Mon, 07 May 2012 07:24:10 -0700 (PDT)
X-BeenThere: repo-discuss@googlegroups.com
Received: by 10.236.149.9 with SMTP id w9ls923791yhj.9.gmail; Mon, 07 May 2012
 07:24:08 -0700 (PDT)
Received: by 10.100.245.33 with SMTP id s33mr6292104anh.4.1336400648569;
        Mon, 07 May 2012 07:24:08 -0700 (PDT)
Received: by 10.100.245.33 with SMTP id s33mr6292103anh.4.1336400648553;
        Mon, 07 May 2012 07:24:08 -0700 (PDT)
Return-Path: <s...@google.com>
Received: from mail-yx0-f174.google.com (mail-yx0-f174.google.com [209.85.213.174])
        by gmr-mx.google.com with ESMTPS id k35si19306325yhb.3.2012.05.07.07.24.08
        (version=TLSv1/SSLv3 cipher=OTHER);
        Mon, 07 May 2012 07:24:08 -0700 (PDT)
Received-SPF: pass (google.com: domain of s...@google.com designates 209.85.213.174 as permitted sender) client-ip=209.85.213.174;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of s...@google.com designates 209.85.213.174 as permitted sender) smtp.mail=...@google.com; dkim=pass header...@google.com
Received: by mail-yx0-f174.google.com with SMTP id m10so3676033yen.19
        for <repo-discuss@googlegroups.com>; Mon, 07 May 2012 07:24:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=google.com; s=20120113;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :cc:content-type:x-system-of-record;
        bh=v5y+ZI5tFPkkv2ZBlvyasmzZvDf6Pga5JM7W29XOeDY=;
        b=dHAWroYhA0weWguul/YEqMtrnBOPSL6GlSVh7D3cvmvQm4hezBt4JKYQUA5tvLLW1T
         3se8edyb4ln3UMuI3tTg4osrH4It8vLu0oK9tl1fwjlFwtpR+SCiodVnWGumWb9rOORH
         WUr5gKeazCn62AiqEak1/90JAK4Ra9lPB0u70++02D8lhxIOW1xESFeahWpyfHUU2euJ
         Q7pAYBvWtZbsoQWN++voHyQYsUC9cayATiHxO6kTzUhVOmLN+rB+1k2Xt4JcWyVB3FXU
         pn4Vet3RaNweF8jROqC9rxzxd3DDhU5p3ssxFtwmRbmpl0lXtADPAm6SzKRqTi4PCrmy
         bG3A==
        d=google.com; s=20120113;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :cc:content-type:x-system-of-record:x-gm-message-state;
        bh=v5y+ZI5tFPkkv2ZBlvyasmzZvDf6Pga5JM7W29XOeDY=;
        b=mOJOG+4JM4MHuJdEjRrjrIAPd5r/ctcoh5zX3qs8WD4c+7CxpWEHpqoUGa4YBQWi7N
         rHcPPxM7MyG9GcvVm7cKwBFrGZB5lMLPibpFB0YIr0MBSvtdNmWZtVP77PhvER9pJsV+
         u22Ci+T99pB0Y+42+ywwMElMSTMwyVPIB6Qv9RADqlJyIbZBYAF2dSdrbLT2qy9iNezF
         3wfJVEDAtEurNYaYdUyk6rWnq3rkY4rYjoJUkWgu+OAq8JEjwYRAdmx2ZYd7f1Ldvves
         XSMyVXKaIl9L9GWs333MPKaadtO+IvhocoCme56Io/dUeAYrAganAgUOn4AIPky6jKeY
         3mEQ==
Received: by 10.50.45.234 with SMTP id q10mr8525792igm.54.1336400648331;
        Mon, 07 May 2012 07:24:08 -0700 (PDT)
Received: by 10.50.45.234 with SMTP id q10mr8525777igm.54.1336400648167; Mon,
 07 May 2012 07:24:08 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.231.205.145 with HTTP; Mon, 7 May 2012 07:23:47 -0700 (PDT)
In-Reply-To: <34b33628-d54f-440b-92e3-1c16401f9...@l15g2000vbv.googlegroups.com>
References: <34b33628-d54f-440b-92e3-1c16401f9...@l15g2000vbv.googlegroups.com>
From: Shawn Pearce <s...@google.com>
Date: Mon, 7 May 2012 07:23:47 -0700
Message-ID: <CAH+XAAqAUY7GCOwjMerJzLd5_mxuDx6E438ZT9Yt1JiEo9e...@mail.gmail.com>
Subject: Re: Can we add users to internal group at once?
To: "seonguk.baek" <baekseon...@gmail.com>
Cc: Repo and Gerrit Discussion <repo-discuss@googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-1
X-System-Of-Record: true
X-Gm-Message-State: ALoCoQkFDSjkBEVBoRVVokPqVnrmNqq7wQEYLP059h5RDRFTk2o8LnHQrwlTMvsIGcUgadpW6+kwztSNFCWJLvmUnHb206tsbQ6hjSns+W5na5UJBPj4jLJNvrN2/MDq8vy44uP3V2oeQzuOvIAEIdyxLFq5H9ECng==

On Sun, May 6, 2012 at 4:44 PM, seonguk.baek <baekseon...@gmail.com> wrote:
> Dear all.
>
> Can we add users to internal group at once?
>
> Gerrit Administrator Commands is only create-project, create-account,
> create-group.
>
> I want to update-group or update-account.
>
> Is there any way to add users to internal group at once?

I don't think so. There are some patches pending for update-account
command that might make this possible over SSH, but these are still
going through the code review process and aren't yet in a release
version.

In the past I have done this using direct SQL to modify the
account_group_members table. After that database change is done, use
`gerrit flush-caches --cache accounts` to force the running server to
reload this table.