From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: sfr@canb.auug.org.au, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: Temporary -rcu tree location
Date: Mon, 12 Sep 2011 17:24:19 -0700 [thread overview]
Message-ID: <20110913002419.GN2362@linux.vnet.ibm.com> (raw)
In-Reply-To: <alpine.LRH.2.00.1109130210090.19238@twin.jikos.cz>
On Tue, Sep 13, 2011 at 02:11:05AM +0200, Jiri Kosina wrote:
> On Mon, 12 Sep 2011, Paul E. McKenney wrote:
>
> > PS. If someone knows how to make github delete a branch, please let me
> > know, as this would allow me to use the "rcu/next" nomenclature.
> > Yes, it is probably obvious, but I am new to github...
>
> git push origin :branch should work everywhere, right?
Here is what happens when I try that:
git push github :rcu/next
Username:
Password:
error: unable to push to unqualified destination: rcu/next
The destination refspec neither matches an existing ref on the remote nor
begins with refs/, and we are unable to guess a prefix based on the source ref.
error: failed to push some refs to 'https://github.com/paulmckrcu/linux'
So what am I missing here?
Thanx, Paul
next prev parent reply other threads:[~2011-09-13 0:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-13 0:01 Temporary -rcu tree location Paul E. McKenney
2011-09-13 0:11 ` Jiri Kosina
2011-09-13 0:24 ` Paul E. McKenney [this message]
2011-09-13 0:43 ` Jiri Kosina
2011-09-13 1:34 ` Paul E. McKenney
2011-09-13 2:07 ` Stephen Rothwell
2011-09-13 4:06 ` Paul E. McKenney
2011-09-13 16:06 ` Paul E. McKenney
2011-09-14 0:20 ` Stephen Rothwell
2011-09-13 0:47 ` Stephen Rothwell
2011-09-13 1:14 ` Stephen Rothwell
2011-09-13 1:21 ` Stephen Rothwell
2011-09-13 1:32 ` Paul E. McKenney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110913002419.GN2362@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.