All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brad Bishop <bradleyb@fuzziesquirrel.com>
To: "Adrian Ambrożewicz" <adrian.ambrozewicz@linux.intel.com>
Cc: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>,
	James Feist <james.feist@linux.intel.com>
Subject: Re: "Initial commit" with entire git history - possible?
Date: Wed, 1 Jul 2020 08:15:54 -0400	[thread overview]
Message-ID: <20200701121554.bfkoh34xxiz7k5hr@thinkpad.dyn.fuzziesquirrel.com> (raw)
In-Reply-To: <c7907f47-db04-12e2-9812-ee72cde822a9@linux.intel.com>

On Wed, Jul 01, 2020 at 01:08:20PM +0200, Adrian Ambrożewicz wrote:
> Brad,
>
> How (as a maintainer) I could 'move' code from our internal repository
> to github/openbmc hosted one? Is it specified somewhere?

git push <remote> HEAD:master

The gerrit remote is something like:
ssh://<user>@gerrit.openbmc-project.xyz:2918/openbmc/telemetry

and the github remote is:
ssh://git@github.com/openbmc/telemetry

You'll need to have configured both github and gerrit to accept whatever
ssh keys you present.

> Currently I've pushed whole code to gerrit as usual review to gather
> feedback, but after that I would still want to pursue path of pushing
> entire git history + review changes on top  of that.

I'm glad to see you are willing to entertain feedback but I'd be
suprised if Intel let you spend time on making any meaningful changes
(e.g. ones that cause significant rework and time investment on your
part) at this point.  This is why code should be developed and reviewed
in the open in the first place if you actually want others to use it.

  reply	other threads:[~2020-07-01 12:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-19  9:10 "Initial commit" with entire git history - possible? Adrian Ambrożewicz
2020-06-19 22:16 ` James Feist
2020-07-01 11:08   ` Adrian Ambrożewicz
2020-07-01 12:15     ` Brad Bishop [this message]
2020-07-06  6:51       ` Adrian Ambrożewicz
2020-07-08 12:14         ` Brad Bishop

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=20200701121554.bfkoh34xxiz7k5hr@thinkpad.dyn.fuzziesquirrel.com \
    --to=bradleyb@fuzziesquirrel.com \
    --cc=adrian.ambrozewicz@linux.intel.com \
    --cc=james.feist@linux.intel.com \
    --cc=openbmc@lists.ozlabs.org \
    /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.