On 6 May 2018 at 09:01, Hervé BOUTEMY wrote:
> uh, the move to trunk discarded the whole history before!
>
> That's not what I expected for a a svn2git mirror
Yes, I already noted that in the related issue:
https://issues.apache.org/jira/browse/INFRA-16355
> I'm not proficient enough in Git and
uh, the move to trunk discarded the whole history before!
That's not what I expected for a a svn2git mirror
I'm not proficient enough in Git and svn2git, I hope infra can help, but it
would be good if we could have the new trunk history appended after the whole
pre-trunk history...
Regards,
H
On 30 April 2018 at 13:41, sebb wrote:
> On 29 April 2018 at 08:40, sebb wrote:
>> Top-posting
>>
>> I have moved SVN down a level to trunk/ and updated the workspace on
>> projects.a.o to use it.
>> Its pubsub seems to be working.
>>
>> The next set of cronjobs run from midnight to 4am (UTC) so
On 29 April 2018 at 08:40, sebb wrote:
> Top-posting
>
> I have moved SVN down a level to trunk/ and updated the workspace on
> projects.a.o to use it.
> Its pubsub seems to be working.
>
> The next set of cronjobs run from midnight to 4am (UTC) so we shall
> see tomorrow if anything needs to be t
Top-posting
I have moved SVN down a level to trunk/ and updated the workspace on
projects.a.o to use it.
Its pubsub seems to be working.
The next set of cronjobs run from midnight to 4am (UTC) so we shall
see tomorrow if anything needs to be tweaked.
S.
On 29 April 2018 at 07:04, sebb wrote:
>
On 26 April 2018 at 01:02, sebb wrote:
> Looks like there is a bit more to it.
>
> asf-auth template needs to be updated to give projects_role access to
> the new directory.
> This can be done by adding the new directory name and later dropping
> the old one.
The asf-auth update has been applied,
Looks like there is a bit more to it.
asf-auth template needs to be updated to give projects_role access to
the new directory.
This can be done by adding the new directory name and later dropping
the old one.
I don't yet know how to update projects-vm safely.
On 25 April 2018 at 12:43, Hervé BO
no objection for me: what is important is to keep the machine running the web
server synchronized with the change
Regards,
Hervé
Le dimanche 22 avril 2018, 10:50:28 CEST sebb a écrit :
> It looks like we need to move the contents of
>
> https://svn.apache.org/repos/asf/comdev/projects.apache.o
It looks like we need to move the contents of
https://svn.apache.org/repos/asf/comdev/projects.apache.org
to
https://svn.apache.org/repos/asf/comdev/projects.apache.org/trunk
[No need to do the same for reporter, as it already uses a trunk directory]
AFAICT this should not affect the projects.
Jira issue created:
https://issues.apache.org/jira/browse/INFRA-16355
Regards,
Hervé
Le samedi 7 avril 2018, 09:36:56 CEST Hervé BOUTEMY a écrit :
> ok, I don't see any remaining objection
>
> I'll ask for svn2git read-only Git+GitHub mirrors.
> Regarding /repos/asf/comdev/site/trunk/, I'll see
ok, I don't see any remaining objection
I'll ask for svn2git read-only Git+GitHub mirrors.
Regarding /repos/asf/comdev/site/trunk/, I'll see if we can name the git repo
"comdev-community.apache.org" to match other "comdev-*.apache.org"
This will ease people understanding that comdev's site is co
yes, they are not mergeable at Git level (since it will be read-only)
but they are mergeable at svn level, the same way that we merge patches
attached to Jira issues (when people take time to create such patches and
attach, which nowadays does not happen much): every GitHub PR can be seen as a
p
Le jeudi 5 avril 2018, 00:42:57 CEST sebb a écrit :
> On 4 April 2018 at 23:34, Hervé BOUTEMY wrote:
> > there is a little misunderstanding: I'm not talking about fully switching
> > from svn to git
> > I'm talking about keeping svn as canonical repository but adding a
> > read-only git mirror lik
The PRs created for read-only hit are not "mergeable"
WBR, Maxim
(from mobile, sorry for the typos)
On Thu, Apr 5, 2018, 05:34 Hervé BOUTEMY wrote:
> there is a little misunderstanding: I'm not talking about fully switching
> from
> svn to git
> I'm talking about keeping svn as canonical reposi
On 4 April 2018 at 23:34, Hervé BOUTEMY wrote:
> there is a little misunderstanding: I'm not talking about fully switching from
> svn to git
> I'm talking about keeping svn as canonical repository but adding a read-only
> git mirror like done on many svn repositories [1]
The JIRA said otherwise..
there is a little misunderstanding: I'm not talking about fully switching from
svn to git
I'm talking about keeping svn as canonical repository but adding a read-only
git mirror like done on many svn repositories [1]
This does not change anything to the host configuration, but adds a GitHub
mir
On 4 April 2018 at 07:09, Hervé BOUTEMY wrote:
> What about creating a Git/GitHub svn2git mirror for projects.apache.org?
> This would be our first Git repo for community/comdev: I don't know which
> prefix
> we should use...
>
> Any objection?
What are the benefits to using Git over SVN?
Do the
What about creating a Git/GitHub svn2git mirror for projects.apache.org?
This would be our first Git repo for community/comdev: I don't know which
prefix
we should use...
Any objection?
Perhaps we can do the same for the 3 other locations in svn
https://projects.apache.org/project.html?comdev-c
Vincent Tuybens created COMDEV-288:
--
Summary: Request "Projects Directory" migration to GIT
Key: COMDEV-288
URL: https://issues.apache.org/jira/browse/COMDEV-288
Project: Community Development
19 matches
Mail list logo
