By the way, a link to this guide in the wiki could be useful for future
reference:
https://git-scm.com/book/en/v2/Git-and-Other-Systems-Migrating-to-Git
On 12 March 2017 at 14:54, Matt Sicker wrote:
> I've imported the repo into git and pushed here:
>
> https://git-wip-us.apache.org/repos/asf/c
I've imported the repo into git and pushed here:
https://git-wip-us.apache.org/repos/asf/commons-pool.git
Web interface: https://git-wip-us.apache.org/repos/asf?p=commons-pool.git
The remaining steps here still need to be done by a PMC (moving old svn
repo into the _moved_to_git directory and th
On Sat, Mar 11, 2017 at 10:02 AM, Matt Sicker wrote:
> Welp, I'm stuck on step one.
>
> $ svn mkdir -m"POOL => Git"
> https://svn.apache.org/repos/asf/commons/_moved_to_git/pool
> svn: E175013: Access to
> '/repos/asf/!svn/txr/1786516-137xq/commons/_moved_to_git/pool' forbidden
>
Done.
Committi
This can only be done by members of the PMC. I'm on my mobile right know.
Can anybody else please jump in?
Benedikt
Matt Sicker schrieb am Sa. 11. März 2017 um 19:07:
> Welp, I'm stuck on step one.
>
> $ svn mkdir -m"POOL => Git"
> https://svn.apache.org/repos/asf/commons/_moved_to_git/pool
> s
Welp, I'm stuck on step one.
$ svn mkdir -m"POOL => Git"
https://svn.apache.org/repos/asf/commons/_moved_to_git/pool
svn: E175013: Access to
'/repos/asf/!svn/txr/1786516-137xq/commons/_moved_to_git/pool' forbidden
On 9 March 2017 at 17:02, Matt Sicker wrote:
> You can use "git svn rebase" to pu
You can use "git svn rebase" to pull down any updates from svn since you
last imported by the way. I used to use git-svn when working with svn
projects here, but that's not a very easy way to perform release management.
On 9 March 2017 at 16:38, sebb wrote:
> On 9 March 2017 at 21:24, Matt Sicke
I made a request the other day to move commons-pool, and they told me it
was all self-serve now and they'd provide help if needed.
On 9 March 2017 at 15:24, Benedikt Ritter wrote:
> Hi,
>
> > Am 09.03.2017 um 21:30 schrieb Oliver Heger <
> oliver.he...@oliver-heger.de>:
> >
> > Hi,
> >
> > Am 09
On 9 March 2017 at 21:24, Matt Sicker wrote:
> The steps are pretty straightforward now:
>
> 1. Do a lazy majority vote to make sure nobody has problems with the
> migration.
> 2. Create a new git repo via the reporeq webapp.
> 3. Get the authors.txt file: https://git-wip-us.apache.org/authors.txt
The steps are pretty straightforward now:
1. Do a lazy majority vote to make sure nobody has problems with the
migration.
2. Create a new git repo via the reporeq webapp.
3. Get the authors.txt file: https://git-wip-us.apache.org/authors.txt
4. Use git-svn to import the subversion repo (there are
Hi,
> Am 09.03.2017 um 21:30 schrieb Oliver Heger :
>
> Hi,
>
> Am 09.03.2017 um 15:58 schrieb Matt Sicker:
>> Thanks! I don't think I'll be able to convert the repo until tomorrow,
>> however.
>
> I would be interested to also move [configuration] to git, but - as
> usual - am pretty busy curr
Hi,
Am 09.03.2017 um 15:58 schrieb Matt Sicker:
> Thanks! I don't think I'll be able to convert the repo until tomorrow,
> however.
I would be interested to also move [configuration] to git, but - as
usual - am pretty busy currently. Is there a documentation somewhere for
the single steps that ne
Thanks! I don't think I'll be able to convert the repo until tomorrow,
however.
On 9 March 2017 at 02:11, Gary Gregory wrote:
> FYI
> -- Forwarded message --
> From:
> Date: Wed, Mar 8, 2017 at 11:25 PM
> Subject: New git mirror created: commons-pool.git
> To: infrastruct...@apa
12 matches
Mail list logo
