> "GS" == Gavin Smith writes:
GS> git svn is going to take a long time to run as it has to connect to the
GS> svn repository for every commit
This is late (I'm catching up on old mail) but one can rsync the savannah
svn repos via rsync://vcs.sv.gnu.org/svn/. A local copy of the repo goes
On Sun, Nov 25, 2018 at 08:18:33PM +0200, Eli Zaretskii wrote:
> > From: Gavin Smith
> > Date: Sun, 25 Nov 2018 17:52:03 +
> > Cc: prein...@logic.at, truer...@trueroad.jp, w...@gnu.org,
> > bug-texinfo@gnu.org
> >
> > > Thanks. Did you migrate the write access from SVN as well? IOW, do I
On Sun, Nov 25, 2018 at 10:02:52PM +0100, Andreas Schwab wrote:
> On Nov 25 2018, Gavin Smith wrote:
>
> > I believe the branches should be cleared up now. Apparently "git svn"
> > creates them all as git branches when they should really be git tags.
>
> svn does not really have a concept of
> > * The main branch is called "trunk" and not "master". (This is probably
> > why pushing worked - there was no branch already existing called
> > "trunk".) The "master" branch is the old 10 years-out-of-date mirror. I
> > believe it is possible to delete the master branch and rename
On Nov 25 2018, Gavin Smith wrote:
> I believe the branches should be cleared up now. Apparently "git svn"
> creates them all as git branches when they should really be git tags.
svn does not really have a concept of tags.
>> The metadata uses svn://127.0.0.1/svn_repo/ instead of
>>
On Sun, Nov 25, 2018 at 10:02:02AM +0900, Norbert Preining wrote:
> git svn clone SVNREPO --no-metadata -A AUTHORSFILE --stdlayout
> ./temp.checkout
> # if there are svn ignore stuff:
> # cd temp.checkout
> # git svn show-ignore > .gitignore
> # git add .gitignore
> # git commit -m 'Convert
> From: Gavin Smith
> Date: Sun, 25 Nov 2018 17:52:03 +
> Cc: prein...@logic.at, truer...@trueroad.jp, w...@gnu.org, bug-texinfo@gnu.org
>
> > Thanks. Did you migrate the write access from SVN as well? IOW, do I
> > have write access to the Git repository, as well as everybody else who
> >
On Sun, Nov 25, 2018 at 06:30:35PM +0200, Eli Zaretskii wrote:
> > From: Gavin Smith
> > Date: Sun, 25 Nov 2018 12:47:09 +
> > Cc: bug-texinfo@gnu.org
> >
> > Hopefully we are nearly there.
> >
> > https://savannah.gnu.org/git/?group=texinfo
>
> Thanks. Did you migrate the write access
> From: Gavin Smith
> Date: Sun, 25 Nov 2018 12:47:09 +
> Cc: bug-texinfo@gnu.org
>
> Hopefully we are nearly there.
>
> https://savannah.gnu.org/git/?group=texinfo
Thanks. Did you migrate the write access from SVN as well? IOW, do I
have write access to the Git repository, as well as
On Nov 25 2018, Gavin Smith wrote:
> There are still some things to do:
>
> * The main branch is called "trunk" and not "master". (This is probably
> why pushing worked - there was no branch already existing called
> "trunk".) The "master" branch is the old 10 years-out-of-date mirror. I
On Sun, Nov 25, 2018 at 10:02:02AM +0900, Norbert Preining wrote:
> What I did with most definitive svn to git conversions is:
>
> git svn clone SVNREPO --no-metadata -A AUTHORSFILE --stdlayout
> ./temp.checkout
> # if there are svn ignore stuff:
> # cd temp.checkout
> # git svn show-ignore >
Hi Gavin,
some comments:
> git svn is going to take a long time to run as it has to connect to the
Yes.
> https://git-scm.com/docs/git-svn recommends against the --no-metadata
> option.
no-metadata is ok if you want to convert definitely to git and
afterwards don't use svn anymore.
I use
On Mon, Nov 19, 2018 at 08:44:43PM +0100, Werner LEMBERG wrote:
> Almost, I think. This guide
>
> https://aboullaite.me/migration-from-svn-to-gitlab/
>
> looks useful.
Google Chrome wouldn't let me see that page because of "inadequate
transport security". :-(
On Tue, Nov 20, 2018 at 09:58:26PM +0900, Masamichi Hosoda wrote:
> > Masamichi-san, how did you do the migration? Maybe Gavin can simply
> > clone your version, which would be the simplest solution, of course.
>
> I used `git svn` something like the followings.
>
> First:
> $ git svn init -s
> Masamichi-san, how did you do the migration? Maybe Gavin can simply
> clone your version, which would be the simplest solution, of course.
I used `git svn` something like the followings.
First:
$ git svn init -s --no-metadata --prefix=svn/ svn://svn.savannah.gnu.org/texinfo
Update:
$ git svn
> There is "svn blame" which you can use to see when each line in a
> file was changed.
Indeed, but useless for me, since it only shows me existing code while
I'm wanting the opposite :-) I could have done manual bisecting, this
is, checking revision by revision until I find the change.
> I'm
On Mon, Nov 19, 2018 at 11:27:04AM +0100, Werner LEMBERG wrote:
> while trying to update lilypond's init script from texi2html version
> 1.82 to 5.0 ??? this is what distributions provide today ??? I wanted to
> find out where function `get_index' was changed. To get all changes
> in the now
On Mon, 19 Nov 2018, Masamichi Hosoda wrote:
> No, I update it manually.
I am doing this via cron scripts and Github deploy ssh keys which allows
me to ignore it completely ;-) Also, it helps with CI testing via
Travis-CI.
Norbert
--
PREINING Norbert
>> Here is a git mirror I've converted.
>> https://github.com/trueroad/texinfo
>
> Ahh, great. Is that automatically/regularly updated?
No, I update it manually.
On Mon, 19 Nov 2018, Masamichi Hosoda wrote:
> Here is a git mirror I've converted.
> https://github.com/trueroad/texinfo
Ahh, great. Is that automatically/regularly updated?
Thanks a lot
Norbert
--
PREINING Norbert http://www.preining.info
Accelia Inc. +
Hi Werner, Norbert, all
>> Given that Savannah provides git support and that it is rather easy to
>> import an SVN repository to git (using `git svn ...') I strongly
>> suggest to migrate to git.
>
> If there is interest, I can set up a git svn mirror as I have done for
> luatex, texlive,
Hi Werner, all
> svn log --diff -r "{2009-01-01}:{2018-11-19}" > ~/texi2html.changes
Umpf, not good. Much faster to do a git svn checkout and then use git.
> Given that Savannah provides git support and that it is rather easy to
> import an SVN repository to git (using `git svn ...') I
Folks,
while trying to update lilypond's init script from texi2html version
1.82 to 5.0 – this is what distributions provide today – I wanted to
find out where function `get_index' was changed. To get all changes
in the now obsolete texi2html directory I issued the following command
(I wasn't
23 matches
Mail list logo
