linux-kernel - Re: Temporary -rcu tree location

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 12 Sep 2011 18:34:00 -0700
From:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To:	Jiri Kosina <jkosina@...e.cz>
Cc:	sfr@...b.auug.org.au, linux-next@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: Temporary -rcu tree location

On Tue, Sep 13, 2011 at 02:43:55AM +0200, Jiri Kosina wrote:
> On Mon, 12 Sep 2011, Paul E. McKenney wrote:
> 
> > 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?
> 
> Looking at 
> 
> 	https://github.com/paulmckrcu/linux/branches
> 
> there doesn't seem to be 'rcu/next' branch, right?

No, there is not.  So the idea is to push "rcu/next" the first time,
then ":rcu/next" thereafter?

							Thanx, Paul
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/