[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [platform-dev] how long will repos remain on gerrit (read-only?)
|
> Thanks. I guess I'll have to prioritize saving all that random work
> somewhere for when (if) I get around to migrating it to PRs
You could simply store them in your github fork, the following should
work (even though I have not tried that out):
1) fork and clone the git repo from github
2) click on the dots-menu in gerrit > Download patch and copy the
'Branch' snippet
3) before execute the command probably choose another name for the branch
4) push that branch to your fork
5) go a haed with the next one ...
That way you have saved at least your code-work and could at any time
open it as a new PR by simply go in the GH page and choose the branch
(maybe you want to rebase it before).
If you like, you can enable issues/discusions/pages/wiki (whatever seems
suitable) in your fork project settings and store e.g. a (m)html, text
copy or individual comments from the gerrit.
Then you are completely independent of EF shuting down, deleting, ... If
you backup your git repo you are even independent of GH shutting down
their service.
If you like to retain all patchsets, it should be possible to branch the
first and then cherry-pick each individual patchset into your branch,
the last number in the refs/... is for the patchset.
Am 17.03.22 um 00:56 schrieb Jonah Graham:
Thanks. I guess I'll have to prioritize saving all that random work
somewhere for when (if) I get around to migrating it to PRs
(sorry for so much WIP - I have a lot more ideas than time to follow up
on all of them)
On Wed., Mar. 16, 2022, 17:32 Aleksandar Kurtakov, <akurtako@xxxxxxxxxx
<mailto:akurtako@xxxxxxxxxx>> wrote:
On Wed, Mar 16, 2022 at 11:15 PM Jonah Graham
<jonah@xxxxxxxxxxxxxxxx <mailto:jonah@xxxxxxxxxxxxxxxx>> wrote:
Hi folks,
How long will the gerrits for platform projects moving to GitHub
be left around? (Sorry if this is asked and answered somewhere else)
We will not let them stay after moving. Process is like
https://git.eclipse.org/r/c/platform/eclipse.platform.team/+/185449
<https://git.eclipse.org/r/c/platform/eclipse.platform.team/+/185449> where
it's abandoned with instruction how to move it to PR. As the repo
becomes read only there is no difference whether it's open or
abandoned, you can recreate it as PR although if not ready it is
better to have it in your own fork.
For how long gerrits will stay it's a question for EF. If the repo
is archived - gerrits are gone. Webmaster team asks for when repo
can be archived in gerrit which we try to delay for Eclipse TLP
repos (doing better than Tycho migration!) but that's beyond us.
I have various WIP gerrits[1] that I hope to come back to one
day. Until now I have considered gerrit a safe place to store
such WIP (as I would my own fork on GitHub).
In addition, the review comments of the gerrits are very
valuable when trying to unravel an old issue.
I ask because some projects that have migrated from gerrit to
GitHub seem to have lost their gerrit entries (Tycho[2]) while
others still live on gerrit (like LSP4E[3])
LSP4E seems to have missed the last step in the migration which
should be fixed and become read-only soon.
[1]
https://git.eclipse.org/r/c/platform/eclipse.platform.debug/+/181035
<https://git.eclipse.org/r/c/platform/eclipse.platform.debug/+/181035>
or https://git.eclipse.org/r/c/equinox/rt.equinox.p2/+/170563
<https://git.eclipse.org/r/c/equinox/rt.equinox.p2/+/170563>
[2] https://git.eclipse.org/r/165496
<https://git.eclipse.org/r/165496> for
https://bugs.eclipse.org/bugs/show_bug.cgi?id=564670
<https://bugs.eclipse.org/bugs/show_bug.cgi?id=564670> is no
longer available
[3] https://git.eclipse.org/r/admin/repos/lsp4e/lsp4e
<https://git.eclipse.org/r/admin/repos/lsp4e/lsp4e>
Thanks
Jonah
~~~
Jonah Graham
Kichwa Coders
www.kichwacoders.com <http://www.kichwacoders.com>
_______________________________________________
platform-dev mailing list
platform-dev@xxxxxxxxxxx <mailto:platform-dev@xxxxxxxxxxx>
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/platform-dev
<https://www.eclipse.org/mailman/listinfo/platform-dev>
--
Aleksandar Kurtakov
Red Hat Eclipse Team
_______________________________________________
platform-dev mailing list
platform-dev@xxxxxxxxxxx <mailto:platform-dev@xxxxxxxxxxx>
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/platform-dev
<https://www.eclipse.org/mailman/listinfo/platform-dev>
_______________________________________________
platform-dev mailing list
platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev