Experimental branches?

[Steven]

I just tried to create an experimental branch for a small project following the steps here:

https://www.chromium.org/developers/experimental-branches

but when I run "git push origin HEAD:refs/experimental/holte/mybranch", I get an error:

 ! [remote rejected] HEAD -> refs/experimental/holte/mybranch (prohibited by Gerrit)

error: failed to push some refs to 'https://chromium.googlesource.com/chromium/src.git'

Is this no longer supported, or am I doing something wrong?

[Jeremy Roman]

Have you set up your .gitcookies to use your credentials (as a committer)? You would have needed to do this to use 'git cl land' or 'git cl dcommit'.

If not, go to https://chromium.googlesource.com/new-password.

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev

[Steven]

Pretty sure I had that set up correctly, and I used git cl land successfully before (~6 months ago), but I got a new cookie and tried again anyway.  Still no luck though.

[Brandon Jones]

I've yet to get the current steps to work, but I've been successfully using instructions from an older version of the page for a while. Dug them out of the history for you:

In Blink, there is a special repository where committers can create Git branches that are accepted as pushes. In this repository, refs/heads/* is kept closely in sync with the official Git mirror, so it is a pretty reliable way to work. Here's the quickstart guide to using this repository, adapted from the original announcement email:

1. Navigate to https://chromium.googlesource.com/, log in with your chromium account, click 'Generate New Password', and follow the instructions.
2. cd <chromium_src>; git remote add -f wip https://chromium.googlesource.com/experimental/chromium/src
3. Hack on some code then commit it locally
4. git push wip HEAD:refs/wip/<chromium username>/foobar, which creates a publicly accessible branch. Any developer can pull with: git fetch wip '+refs/wip/<chromium username>/foobar:refs/heads/foobar'

Please restrict pushes to the refs/wip namespace, specifically in the

following format: refs/wip/<username or codeword>/<branch name>

On Tue, Jun 28, 2016 at 2:24 PM Steven <ho...@chromium.org> wrote:

Pretty sure I had that set up correctly, and I used git cl land successfully before (~6 months ago), but I got a new cookie and tried again anyway.  Still no luck though.

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev

---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.

[Matt Giuca]

It's perhaps worth pointing out that this flow should *not* be done for an experimental feature. Experiments should generally be done on trunk, behind a flag (so even if users aren't seeing them, they are being compiled and tested by all the users and bots and won't rot).

I guess the exception is if you are experimenting with the code itself (i.e., a big refactor).

[Steven]

Thanks, those steps worked for me!

Mostly using this to share some debug / proof of concept code with a couple collaborators, not an experimental feature.

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev+unsubscribe@chromium.org.

[Vinod kumar Sonkusare]

https://youtu.be/f2mV2S7qTa4

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.

[Vincent Scheib]

If it helps, github works easily to collaborate, share code between machines, just have a backup, etc; and is simple to use and mange.

Fork

  https://github.com/scheib/chromium

to get started (much easier than pushing the whole repo yourself)

On your branches page, similar to this:

  https://github.com/scheib/chromium/branches

trash all my branches that you won't need.

Then just 

git remote add; and git push using the normal github flow.

On Thu, Jun 30, 2016 at 8:26 AM, Koshthi Hemraj Ghanshyam <koshth...@gmail.com> wrote:

What about the raspberry with chrome is?