Besides adding the Beaker Gerrit remote in your .git/config [1], you can also define a BASH function such as:
# git push function git-push(){ git push git+ssh://gerrit.beaker-project.org:29418/beaker "$@":refs/for/develop; }
And then to push a branch 908174, simply $ git-push 908174
[1] http://beaker-project.org/dev/guide/writing-a-patch.html#submitting-your-pat...
Best, -Amit.
On 06/05/2013 02:42 PM, Amit Saha wrote:
Besides adding the Beaker Gerrit remote in your .git/config [1], you can also define a BASH function such as:
# git push function git-push(){ git push git+ssh://gerrit.beaker-project.org:29418/beaker "$@":refs/for/develop; }
And then to push a branch 908174, simply $ git-push 908174
[1] http://beaker-project.org/dev/guide/writing-a-patch.html#submitting-your-pat...
Nice. I currently just use Ctrl-R (to bring up the search prompt for my bash command history) and then start typing "refs/for"
That will usually give me the right local branch (maybe hitting Ctrl-R another couple of times), and if that doesn't work, then I'll usually have a "git status" output not far above to copy and paste the branch name from.
When naming a bug branch, I also include a short description in the name so I don't have to remember what the bug number refers to:
$ git branch * beaker-0.13-release-notes bz880855_fix_repo_snapshots bz921346_included_task_docs_review bz950895_scheduler_rollback bz957577_valid_namespace_pkg bz961206_protect_system_groups bz961580_group_job_access bz969959_ldap_refresh_docs develop master ovirt_warning pure_virt_testing
Cheers, Nick.
----- Original Message -----
From: "Nick Coghlan" ncoghlan@redhat.com To: beaker-devel@lists.fedorahosted.org Sent: Wednesday, June 5, 2013 2:58:53 PM Subject: Re: [Beaker-devel] 2-c tip: BASH function for pushing patches
On 06/05/2013 02:42 PM, Amit Saha wrote:
Besides adding the Beaker Gerrit remote in your .git/config [1], you can also define a BASH function such as:
# git push function git-push(){ git push git+ssh://gerrit.beaker-project.org:29418/beaker "$@":refs/for/develop; }
And then to push a branch 908174, simply $ git-push 908174
[1] http://beaker-project.org/dev/guide/writing-a-patch.html#submitting-your-pat...
Nice. I currently just use Ctrl-R (to bring up the search prompt for my bash command history) and then start typing "refs/for"
That will usually give me the right local branch (maybe hitting Ctrl-R another couple of times), and if that doesn't work, then I'll usually have a "git status" output not far above to copy and paste the branch name from.
That sounds like me before i decided to add this. Although, I searched for few things: 'push', 'ssh', 'git' .. , whichever returned what i was looking for :-)
-Amit.
Excerpts from Nick Coghlan's message of 2013-06-05 14:58:53 +1000:
When naming a bug branch, I also include a short description in the name so I don't have to remember what the bug number refers to:
Our very own Peter Hutterer wrote some helper scripts for that:
http://who-t.blogspot.com.au/2013/03/git-branch-tools-some-helpers-for.html
----- Original Message -----
From: "Dan Callaghan" dcallagh@redhat.com To: "beaker-devel" beaker-devel@lists.fedorahosted.org Sent: Wednesday, June 5, 2013 3:07:59 PM Subject: Re: [Beaker-devel] 2-c tip: BASH function for pushing patches
Excerpts from Nick Coghlan's message of 2013-06-05 14:58:53 +1000:
When naming a bug branch, I also include a short description in the name so I don't have to remember what the bug number refers to:
Our very own Peter Hutterer wrote some helper scripts for that:
http://who-t.blogspot.com.au/2013/03/git-branch-tools-some-helpers-for.html
Nice!
beaker-devel@lists.fedorahosted.org