On Do, 27 Aug 2015, Markus Heidelberg wrote:
> The git repository doesn't need it and you can't even test the .hgignore
> file in the git repository for correct syntax. There might be subtle
> differences, I don't know exactly. I think this is best be left to the
> HG mirror to convert .gitignore
Am Mittwoch, 26. August 2015, 20:08:11 schrieb Ben Fritz:
> On Tuesday, August 25, 2015 at 12:55:29 PM UTC-5, Markus Heidelberg wrote:
> > Am Dienstag, 25. August 2015, 17:42:26 schrieb Christian Brabandt:
> > >
> > > Did the .gitignore file change between the old googlecode repository and
> > >
On Tuesday, August 25, 2015 at 12:55:29 PM UTC-5, Markus Heidelberg wrote:
> Am Dienstag, 25. August 2015, 17:42:26 schrieb Christian Brabandt:
> >
> > Did the .gitignore file change between the old googlecode repository and
> > the new github repository? I get a modification here:
> >
> > diff
Christian Brabandt wrote:
> On Do, 20 Aug 2015, Bram Moolenaar wrote:
>
> > I have done the "for real" update of the Vim repository.
> > I used the same sequence of commands as for the tryout, thus the result
> > should be the same.
>
> Did the .gitignore file change between the old googlecode
Am Dienstag, 25. August 2015, 17:42:26 schrieb Christian Brabandt:
>
> Did the .gitignore file change between the old googlecode repository and
> the new github repository? I get a modification here:
>
> diff --git a/.gitignore b/.gitignore
> --- a/.gitignore
> +++ b/.gitignore
> @@ -1,5 +1,3 @@
On Di, 25 Aug 2015, Christian Brabandt wrote:
> On Do, 20 Aug 2015, Bram Moolenaar wrote:
>
> > I have done the "for real" update of the Vim repository.
> > I used the same sequence of commands as for the tryout, thus the result
> > should be the same.
>
> Did the .gitignore file change between
On Do, 20 Aug 2015, Bram Moolenaar wrote:
> I have done the "for real" update of the Vim repository.
> I used the same sequence of commands as for the tryout, thus the result
> should be the same.
Did the .gitignore file change between the old googlecode repository and
the new github repository?
* Bram Moolenaar [150821 16:39]:
> The idea is that all events on GitHub are forwarded to the vimdev
> maillist. Christian had setup something for that. I believe this also
> applies to pull requests.
>
> I indeed prefer to discuss changes on the maillist, since everybody can
> join and it keep
Marvin Reply wrote:
> There was a longish thread on debian-devel a while back (I can't find it
> right now) about using github for development. One of the points raised
> was that if you accept github pull requests (from their web UI), then
> those developers who do not have (and perhaps do not
* Bram Moolenaar [150821 14:59]:
> Looks like most things are ready, I'll soon announce that GitHub is
> ready for our business.
>
> What remains to be filled in is the section "Moving over to github - if
> you have local changes" on http://www.vim.org/movetogithub.php
> Who has a good text for t
Christian Brabandt wrote:
> On Do, 20 Aug 2015, Christian Brabandt wrote:
>
> > On Do, 20 Aug 2015, Bram Moolenaar wrote:
> >
> > > http://www.vim.org/develop.php
>
> also, I think sources.php needs to be adjusted as well.
Looks like most things are ready, I'll soon announce that GitHub is
re
Christian Brabandt wrote:
> On Do, 20 Aug 2015, Christian Brabandt wrote:
>
> > On Do, 20 Aug 2015, Bram Moolenaar wrote:
> >
> > > http://www.vim.org/develop.php
>
> also, I think sources.php needs to be adjusted as well.
Yes, I'll do that.
--
BEDEVERE: Oh!
LAUNCELOT: No "Arrg
Christian Brabandt wrote:
> On Do, 20 Aug 2015, Bram Moolenaar wrote:
>
> > http://www.vim.org/develop.php
>
> There is a link missing for the "mercurial mirror on bitbucket"
Added.
However, I think we should move the stuff about using MQ to the
Mercurial page.
> I would prefer to have a sec
Hi vim_dev!
On Do, 20 Aug 2015, Christian Brabandt wrote:
> On Do, 20 Aug 2015, Bram Moolenaar wrote:
>
> > http://www.vim.org/develop.php
also, I think sources.php needs to be adjusted as well.
Best,
Christian
--
Astrologe:
ein Mensch, der aus den Sternen liest, was im Gesicht steht.
--
On Do, 20 Aug 2015, Bram Moolenaar wrote:
> http://www.vim.org/develop.php
There is a link missing for the "mercurial mirror on bitbucket"
I would prefer to have a section on how to migrate from google code to
bitbucket / git.
And if some git expert could write a short explanation on how to de
Markus Heidelberg wrote:
> > The biggest file there is 33M. No idea how it gets bigger after pushing
> > to GitHub. 10M is not something to worry about. Previously it was
> > 600M.
>
> Maybe it has something to do with GitHub's repository management. Or
> that the repository was not empty whe
On Wednesday, August 19, 2015 at 9:03:52 AM UTC-4, Olaf wrote:
> On 19-Aug-15, Bram Moolenaar wrote:
> >
> > Justin M. Keyes wrote:
...
> > > Why was the _mercurial_ tag format changed in the google code
> > > repository? This breaks all URLs using the old tag format:
> > >
> > > https://code.goo
Am Donnerstag, 20. August 2015, 10:55:23 schrieb Bram Moolenaar:
>
> Markus Heidelberg wrote:
>
> > Am Mittwoch, 19. August 2015, 23:15:14 schrieb Markus Heidelberg:
> > > Am Mittwoch, 19. August 2015, 21:35:52 schrieb Bram Moolenaar:
> > > >
> > > > I have removed the Ubuntu package for hg-fast
Am Donnerstag, 20. August 2015, 10:09:39 schrieb Manuel Ortega:
> On Thu, Aug 20, 2015 at 4:55 AM, Bram Moolenaar wrote:
>
> >
> > Markus Heidelberg wrote:
> >
> > > Am Mittwoch, 19. August 2015, 23:15:14 schrieb Markus Heidelberg:
> > > > Am Mittwoch, 19. August 2015, 21:35:52 schrieb Bram Moole
On Thu, Aug 20, 2015 at 4:55 AM, Bram Moolenaar wrote:
>
> Markus Heidelberg wrote:
>
> > Am Mittwoch, 19. August 2015, 23:15:14 schrieb Markus Heidelberg:
> > > Am Mittwoch, 19. August 2015, 21:35:52 schrieb Bram Moolenaar:
>
> > > I cloned it - it is perfect :)
>
For some reason on github.com
Markus Heidelberg wrote:
> Am Mittwoch, 19. August 2015, 23:15:14 schrieb Markus Heidelberg:
> > Am Mittwoch, 19. August 2015, 21:35:52 schrieb Bram Moolenaar:
> > >
> > > I have removed the Ubuntu package for hg-fast-export and downloaded the
> > > individual files from repo.or.cz. The convers
On Wed, Aug 19, 2015 at 7:25 PM, Markus Heidelberg
wrote:
> Am Mittwoch, 19. August 2015, 19:00:36 schrieb Justin M. Keyes:
>> On Aug 19, 2015 5:57 PM, "Markus Heidelberg"
>> wrote:
>> >
>> > Am Mittwoch, 19. August 2015, 15:03:38 schrieb Olaf Dabrunz:
>> > > On 19-Aug-15, Bram Moolenaar wrote:
>
Am Mittwoch, 19. August 2015, 19:00:36 schrieb Justin M. Keyes:
> On Aug 19, 2015 5:57 PM, "Markus Heidelberg"
> wrote:
> >
> > Am Mittwoch, 19. August 2015, 15:03:38 schrieb Olaf Dabrunz:
> > > On 19-Aug-15, Bram Moolenaar wrote:
> > > >
> > > > Justin M. Keyes wrote:
> > > >
> > > > > On 8/18/15
On Aug 19, 2015 5:57 PM, "Markus Heidelberg"
wrote:
>
> Am Mittwoch, 19. August 2015, 15:03:38 schrieb Olaf Dabrunz:
> > On 19-Aug-15, Bram Moolenaar wrote:
> > >
> > > Justin M. Keyes wrote:
> > >
> > > > On 8/18/15, Bram Moolenaar wrote:
> > > > >
> > > > > There were a couple of hiccups, but t
Am Mittwoch, 19. August 2015, 23:15:14 schrieb Markus Heidelberg:
> Am Mittwoch, 19. August 2015, 21:35:52 schrieb Bram Moolenaar:
> >
> > I have removed the Ubuntu package for hg-fast-export and downloaded the
> > individual files from repo.or.cz. The conversion now runs without any
> > errors o
Am Mittwoch, 19. August 2015, 15:03:38 schrieb Olaf Dabrunz:
> On 19-Aug-15, Bram Moolenaar wrote:
> >
> > Justin M. Keyes wrote:
> >
> > > On 8/18/15, Bram Moolenaar wrote:
> > > >
> > > > There were a couple of hiccups, but the repository has moved to GitHub
> > > > now. It's in the destinati
Am Mittwoch, 19. August 2015, 21:35:52 schrieb Bram Moolenaar:
>
> I have removed the Ubuntu package for hg-fast-export and downloaded the
> individual files from repo.or.cz. The conversion now runs without any
> errors or warnings.
>
> The result is now available at https://github.com/vim/vim-t
Am Mittwoch, 19. August 2015, 11:59:12 schrieb Bram Moolenaar:
>
> Markus Heidelberg wrote:
>
> > Am Dienstag, 18. August 2015, 18:42:50 schrieb Bram Moolenaar:
> > >
> > > I let the script continue, ignoring the errors. Then I pushed the
> > > result to github. I got some errors, I think my s
Markus Heidelberg wrote:
> Am Dienstag, 18. August 2015, 18:42:50 schrieb Bram Moolenaar:
> >
> > I wrote:
> >
> > > Applying your git cleanup script after the conversion from hg to git
> > > produces lots of these errors:
> > >
> > > fatal: ambiguous argument 'v7.2.434~4': unknown revision or
On 19-Aug-15, Bram Moolenaar wrote:
>
> Justin M. Keyes wrote:
>
> > On 8/18/15, Bram Moolenaar wrote:
> > >
> > > There were a couple of hiccups, but the repository has moved to GitHub
> > > now. It's in the destination place: https://github.com/vim/vim
> > >
> > > Now we need to do the git cl
Justin M. Keyes wrote:
> On 8/18/15, Bram Moolenaar wrote:
> >
> > There were a couple of hiccups, but the repository has moved to GitHub
> > now. It's in the destination place: https://github.com/vim/vim
> >
> > Now we need to do the git cleanup. I'll hold off until it looks OK,
> > https://g
Markus Heidelberg wrote:
> Am Dienstag, 18. August 2015, 18:42:50 schrieb Bram Moolenaar:
> >
> > I wrote:
> >
> > > Applying your git cleanup script after the conversion from hg to git
> > > produces lots of these errors:
> > >
> > > fatal: ambiguous argument 'v7.2.434~4': unknown revision or
On 8/18/15, Bram Moolenaar wrote:
>
> There were a couple of hiccups, but the repository has moved to GitHub
> now. It's in the destination place: https://github.com/vim/vim
>
> Now we need to do the git cleanup. I'll hold off until it looks OK,
> https://github.com/vim/vim-tryout is what it wou
On 18-Aug-15, Christian Brabandt wrote:
> Here is a documentation update:
>
> Stay with mercurial
> ===
>
> A repository at bitbucket.org has been setup that mirrors the official Vim
> source repository at https://github.com/vim/vim
Minor nit-pick:
"has been setup" -> "has
There were a couple of hiccups, but the repository has moved to GitHub
now. It's in the destination place: https://github.com/vim/vim
Now we need to do the git cleanup. I'll hold off until it looks OK,
https://github.com/vim/vim-tryout is what it would look like.
At least it doesn't have the ol
Am Dienstag, 18. August 2015, 18:42:50 schrieb Bram Moolenaar:
>
> I wrote:
>
> > Applying your git cleanup script after the conversion from hg to git
> > produces lots of these errors:
> >
> > fatal: ambiguous argument 'v7.2.434~4': unknown revision or path not in the
> > working tree.
> > Use
Christian Brabandt wrote:
> On Di, 18 Aug 2015, Bram Moolenaar wrote:
>
> > Note: I have started doing things "for real".
> > The cleaned up Mercurial repository has been pushed to Google code.
>
> I have resynced the bitbucket mirror. I will update the sync script
> tomorrow, when the new gith
On Di, 18 Aug 2015, Bram Moolenaar wrote:
> Note: I have started doing things "for real".
> The cleaned up Mercurial repository has been pushed to Google code.
I have resynced the bitbucket mirror. I will update the sync script
tomorrow, when the new github repository should be available. And onc
Note: I have started doing things "for real".
The cleaned up Mercurial repository has been pushed to Google code.
I'll now start the export to github. We can redo this when needed.
In preparation I've renamed the previously exported repo, which was
overwritten with the cleaned up one, to vim-try
On 18 August 2015, Bram Moolenaar wrote:
>
> Lcd wrote:
>
> > On 18 August 2015, Bram Moolenaar wrote:
> > [...]
> > > For users who switch from Mercurial on Google Code to the Mercurial
> > > mirror, there would be an extra commit that doesn't exist anywhere
> > > else. I hope that will work.
I wrote:
> Applying your git cleanup script after the conversion from hg to git
> produces lots of these errors:
>
> fatal: ambiguous argument 'v7.2.434~4': unknown revision or path not in the
> working tree.
> Use '--' to separate paths from revisions, like this:
> 'git [...] -- [...]'
>
> I
Lcd wrote:
> On 18 August 2015, Bram Moolenaar wrote:
> [...]
> > For users who switch from Mercurial on Google Code to the Mercurial
> > mirror, there would be an extra commit that doesn't exist anywhere
> > else. I hope that will work.
> [...]
>
> Why not make the Bitbucket mirror at the
Markus -
Applying your git cleanup script after the conversion from hg to git
produces lots of these errors:
fatal: ambiguous argument 'v7.2.434~4': unknown revision or path not in the
working tree.
Use '--' to separate paths from revisions, like this:
'git [...] -- [...]'
I'll have a look my
On 18 August 2015, Bram Moolenaar wrote:
[...]
> For users who switch from Mercurial on Google Code to the Mercurial
> mirror, there would be an extra commit that doesn't exist anywhere
> else. I hope that will work.
[...]
Why not make the Bitbucket mirror at the same time as the Github
migr
Markus Heidelberg wrote:
> > Wonderful! And just in time, I'm working on Vim today.
>
> Then staying up late was worth it :)
And thanks for checking the plan.
> > So, these are the steps to be taken:
> > 1. Stop making changes: "freeze"; announce on Google code project page.
> >Announce o
Am 2015-08-18 14:56, schrieb Markus Heidelberg:
7. Commit a change in the Mercurial repo to break the build, pointing
the user
to github. Do NOT push this yet.
8. Convert the Mercurial repo to github.
9. Commit a change that undoes the build breakage.
10. Run the git cleanup script: ~/tmp/cl
I hope I don't brake the mail chain, I'm not at home at my mail client.
> Wonderful! And just in time, I'm working on Vim today.
Then staying up late was worth it :)
> So, these are the steps to be taken:
> 1. Stop making changes: "freeze"; announce on Google code project page.
>Announce on
Markus Heidelberg wrote:
> Am Sonntag, 16. August 2015, 15:23:15 schrieb Bram Moolenaar:
> >
> > OK, if there is a chance you still find some improvements for the
> > Mercurial cleanup, we better wait a bit before doing that.
> >
> > Once you have it all figured out, I hope you can send me the
ore and after each step.
#!/bin/bash
# Vim HG repository cleanup
#
# Overview:
# - close stale branches
# - fix wrong tags
# - remove unused tags
# - add missing tags
# - rename tags: replace - by .
set -e
hg config extensions.rebase || { echo -e "Rebase extension has to be enabled in
~/
Am Montag, 17. August 2015, 14:49:51 schrieb Marius Gedminas:
> On Fri, Aug 14, 2015 at 01:39:18AM +0200, Markus Heidelberg wrote:
> > Am Donnerstag, 13. August 2015, 13:14:34 schrieb Bram Moolenaar:
> > > You mentioned the size of the repository after "export to github" was
> > > much larger than
Markus Heidelberg wrote:
> > > Maybe you can comment on some other items from the old mail as well.
> >
> > Can you repeat the relevant questions?
>
> Oh, not that many remaining which needed clarification. New comments by
> myself compared to the old mail after "MH":
>
> * Unify name and mail
On Fri, Aug 14, 2015 at 01:39:18AM +0200, Markus Heidelberg wrote:
> Am Donnerstag, 13. August 2015, 13:14:34 schrieb Bram Moolenaar:
> > You mentioned the size of the repository after "export to github" was
> > much larger than the one resulting from the local conversion. How do
> > you see that?
you can send me the final
> scripts. I wouldn't want some small mistake spoil the fun.
OK.
> > In my initial mail about repository cleanup from 2015-04-01 I added the
> > following item:
> >
> > * Rename tags to match the normal version notation:
> > s/-/./
ind some improvements for the
Mercurial cleanup, we better wait a bit before doing that.
Once you have it all figured out, I hope you can send me the final
scripts. I wouldn't want some small mistake spoil the fun.
> In my initial mail about repository cleanup from 2015-04-01 I added th
On So, 16 Aug 2015, Markus Heidelberg wrote:
> Am Freitag, 14. August 2015, 09:42:34 schrieb Christian Brabandt:
> > On Fr, 14 Aug 2015, Markus Heidelberg wrote:
> >
> > > I'd also prefer to just removing the .hgignore from the history and
> > > replacing it with .gitignore. What would that mean
f9d121ff99eb2e1697a35dca528e7ecb8f4c v7-2-442
hg tag -f -r 0c1e413c32f1f3f8e28ebf8a030cedeeb664cd46 v7-2-443
hg tag -f -r b619655b31db9469f6fe41932daff7a566079097 v7-2-446
+hg tag -f -r afb476746692322523f167c218803317b87623e3 v7-3-143
hg tag -f -r 353442863d8558dc89d35ef349b60ebb2e38de0e v7-4-415
h
Am Freitag, 14. August 2015, 09:42:34 schrieb Christian Brabandt:
> Hi Markus!
>
> On Fr, 14 Aug 2015, Markus Heidelberg wrote:
>
> > I'd also prefer to just removing the .hgignore from the history and
> > replacing it with .gitignore. What would that mean for the HG mirror,
> > Christian?
>
> H
Matthew Woehlke wrote:
> On 2015-08-14 14:38, Bram Moolenaar wrote:
> > Hmm, one can add a repository and delete a repository, but making it
> > totally empty and pushing a fresh repo into it appears not to be
> > possible.
>
> As far as non-git content (e.g. issues, pull requests), that may be
Markus Heidelberg wrote:
> > > > > Oh, I just noticed, of course we cannot just use a new git
> > > > > repository/project on GitHub, otherwise the issues are gone.
> > > > > The final official repository has to be pushed to one created by the
> > > > > Google exporter therefore.
> > > >
> > > >
Am Freitag, 14. August 2015, 20:38:49 schrieb Bram Moolenaar:
>
> Markus Heidelberg wrote:
>
> > > > Oh, I just noticed, of course we cannot just use a new git
> > > > repository/project on GitHub, otherwise the issues are gone.
> > > > The final official repository has to be pushed to one create
On 2015-08-14 14:38, Bram Moolenaar wrote:
> Hmm, one can add a repository and delete a repository, but making it
> totally empty and pushing a fresh repo into it appears not to be
> possible.
As far as non-git content (e.g. issues, pull requests), that may be true.
To empty out the git bits of a
Markus Heidelberg wrote:
> > > Oh, I just noticed, of course we cannot just use a new git
> > > repository/project on GitHub, otherwise the issues are gone.
> > > The final official repository has to be pushed to one created by the
> > > Google exporter therefore.
> >
> > For the one that's ther
Am Freitag, 14. August 2015, 15:05:41 schrieb Bram Moolenaar:
>
> Markus Heidelberg wrote:
>
> > Am Freitag, 14. August 2015, 01:39:18 schrieb Markus Heidelberg:
> > > Am Donnerstag, 13. August 2015, 13:14:34 schrieb Bram Moolenaar:
> > > >
> > > > Markus Heidelberg wrote:
> > > >
> > > > [...]
Markus Heidelberg wrote:
> > > OK, then I would document a procedure for local HG to Git conversion and
> > > create a script for Git repository cleanup.
> >
> > I did:
> >
> > % mkdir vim-git
> > % cd vim-git
> > % git init
Markus Heidelberg wrote:
> Am Freitag, 14. August 2015, 01:39:18 schrieb Markus Heidelberg:
> > Am Donnerstag, 13. August 2015, 13:14:34 schrieb Bram Moolenaar:
> > >
> > > Markus Heidelberg wrote:
> > >
> > > [...]
> > >
> > > > > > 2. Conversion from HG to Git
> > > > > > ***
Hi Markus!
On Fr, 14 Aug 2015, Markus Heidelberg wrote:
> I'd also prefer to just removing the .hgignore from the history and
> replacing it with .gitignore. What would that mean for the HG mirror,
> Christian?
Hm, I don't know. I guess I can keep it checked in and let git ignore
it.
Best,
Chr
Am Freitag, 14. August 2015, 01:39:18 schrieb Markus Heidelberg:
> Am Donnerstag, 13. August 2015, 13:14:34 schrieb Bram Moolenaar:
> >
> > Markus Heidelberg wrote:
> >
> > [...]
> >
> > > > > 2. Conversion from HG to Git
> > > > >
> > > > >
> > > >
> > > > So, wha
Am Donnerstag, 13. August 2015, 23:01:07 schrieb Bram Moolenaar:
>
> Markus Heidelberg wrote:
>
> > OK, then I would document a procedure for local HG to Git conversion and
> > create a script for Git repository cleanup.
>
> I did:
>
> % mkdir vim-git
>
published repo):
$ git gc
> > > > 3. Cleanup in the Git repository
> > > >
> > > >
> > > > There were suggestions to use the Git mirror from vim-jp as base for the
> > > > official repository, don't k
Markus Heidelberg wrote:
> OK, then I would document a procedure for local HG to Git conversion and
> create a script for Git repository cleanup.
I did:
% mkdir vim-git
% cd vim-git
% git init
% hg-fast-export -r ../hg-vim74-clean
% git checkout
Looks like it
repository
> > >
> > >
> > > There were suggestions to use the Git mirror from vim-jp as base for the
> > > official repository, don't know if this is still an option.
> >
> > Only if there are real advantages. I
e this is going to be the new root for what everybody uses,
> we better make sure this is a clean repository.
Exactly!
> > 3. Cleanup in the Git repository
> >
> >
> > There were suggestions to use the Git mirror from vim-jp as base
Christian Brabandt wrote:
> On Sa, 08 Aug 2015, Bram Moolenaar wrote:
>
> > I would rather not take the risk of messing up the Mercurial repository.
> > Thus would the best approach be to do the conversion locally and replace
> > the git repository on github? We could even try that out now, sin
Markus Heidelberg wrote:
> sorry for the late reply. I'm pretty busy and also needed a bit to find
> the proper words. It also takes some time to get into this topic again
> after several months of silence.
Thanks for the long reply.
> Am Samstag, 8. August 2015, 21:43:13 schrieb Bram Moolenaar
Am Mittwoch, 12. August 2015, 08:50:55 schrieb Nazri Ramliy:
> On Wed, Aug 12, 2015 at 6:51 AM, Markus Heidelberg > #!/bin/sh
> > # Vim HG repository cleanup
> >
> > hg config extensions.rebase || (echo -e "Rebase extension has to be enabled
> > in ~/.hgrc:
On Wed, Aug 12, 2015 at 6:51 AM, Markus Heidelberg > #!/bin/sh
> # Vim HG repository cleanup
>
> hg config extensions.rebase || (echo -e "Rebase extension has to be enabled
> in ~/.hgrc:\n[extensions]\nrebase =" && exit 1)
The "exit 1" above won&
y.
I invested quite a bit of time and I'm not eager to change the HG
cleanup into a Git cleanup, having lots of the spent time wasted.
The cleanup script runs locally on your local repository as described
above. There is nothing, which can be messed up without being able to
recognize it in the resu
On Sa, 08 Aug 2015, Bram Moolenaar wrote:
> I would rather not take the risk of messing up the Mercurial repository.
> Thus would the best approach be to do the conversion locally and replace
> the git repository on github? We could even try that out now, since the
> github repository is for test
I wrote:
> Markus Heidelberg wrote:
>
> > For me, a proper project history from developer view is equal to good
> > documentation from user view.
>
> It's been some since we looked at this, and the information is now
> scattered over several messages.
>
> Markus, could you make the step-by-ste
Markus Heidelberg wrote:
> For me, a proper project history from developer view is equal to good
> documentation from user view.
It's been some since we looked at this, and the information is now
scattered over several messages.
Markus, could you make the step-by-step description of what needs
On 4/16/2015 1:33 PM, Nikolay Pavlov wrote:
More powerful?! Try to add phases/changeset obsolescense/branches/etc to git.
The point is that this “sharper knife” has an architecture that
prevents adding feature to the core. You can do almost anything with
the core using plugins for mercurial, bu
2015-04-16 9:36 GMT+03:00 Roland Eggner :
> On 2015-04-14 Tuesday at 20:00 +0300 Nikolay Pavlov wrote:
>> 2015-04-14 17:37 GMT+03:00 Roland Eggner :
>> > @Bram, @Christian, @all
>> > ───
>> > During some 10 years of almost daily usage of mercurial I have learned, I
>> > can
>>
On 2015-04-14 Tuesday at 20:00 +0300 Nikolay Pavlov wrote:
> 2015-04-14 17:37 GMT+03:00 Roland Eggner :
> > @Bram, @Christian, @all
> > ───
> > During some 10 years of almost daily usage of mercurial I have learned, I
> > can
> > usefully apply the philosophy, which Bram has pr
On 2015-04-15 Wednesday at 18:41 +0200 Bram Moolenaar wrote:
>
> Roland Eggner wrote:
>
> [...]
>
> > @Bram
> > ─
> > As you prefer context over unified diff format:
>
> Only for the patches I send out. If someone sends me a patch any format
> will do.
>
> > • Are you aware of the possib
Hi Markus!
On Mi, 15 Apr 2015, Markus Heidelberg wrote:
> Am Dienstag, 14. April 2015, 20:02:17 schrieb Christian Brabandt:
> > Ubuntu 12.04 LTS:
> > Mercurial Distributed SCM (version 2.0.2)
> > (see http://mercurial.selenic.com for more information)
>
> Huh, pretty old from 2012-01-01 :)
You
Roland Eggner wrote:
[...]
> @Bram
> ─
> As you prefer context over unified diff format:
Only for the patches I send out. If someone sends me a patch any format
will do.
> • Are you aware of the possibility, that both git and mercurial can be
>configured to output _every_ diff out
Hello Christian and Nikolay
Am Dienstag, 14. April 2015, 20:02:17 schrieb Christian Brabandt:
> On Di, 14 Apr 2015, Nikolay Pavlov wrote:
>
> > 2015-04-14 20:45 GMT+03:00 Christian Brabandt :
> > > Hi Markus!
> > >
> > > On Mo, 13 Apr 2015, Markus Heidelberg wrote:
> > >
> > > [...]
> > >> hg reb
2015-04-14 21:50 GMT+03:00 Nikolay Pavlov :
> 2015-04-14 21:36 GMT+03:00 Christian Brabandt :
>>
>> On Di, 14 Apr 2015, Nikolay Pavlov wrote:
>>> 2015-04-14 21:02 GMT+03:00 Christian Brabandt :
>>> > On Di, 14 Apr 2015, Nikolay Pavlov wrote:
>>> >
>>> >> 2015-04-14 20:45 GMT+03:00 Christian Braband
2015-04-14 21:36 GMT+03:00 Christian Brabandt :
>
> On Di, 14 Apr 2015, Nikolay Pavlov wrote:
>> 2015-04-14 21:02 GMT+03:00 Christian Brabandt :
>> > On Di, 14 Apr 2015, Nikolay Pavlov wrote:
>> >
>> >> 2015-04-14 20:45 GMT+03:00 Christian Brabandt :
>> >> > Hi Markus!
>> >> >
>> >> > On Mo, 13 Apr
On Di, 14 Apr 2015, Nikolay Pavlov wrote:
> 2015-04-14 21:02 GMT+03:00 Christian Brabandt :
> > On Di, 14 Apr 2015, Nikolay Pavlov wrote:
> >
> >> 2015-04-14 20:45 GMT+03:00 Christian Brabandt :
> >> > Hi Markus!
> >> >
> >> > On Mo, 13 Apr 2015, Markus Heidelberg wrote:
> >> >
> >> > [...]
> >> >
2015-04-14 21:02 GMT+03:00 Christian Brabandt :
> On Di, 14 Apr 2015, Nikolay Pavlov wrote:
>
>> 2015-04-14 20:45 GMT+03:00 Christian Brabandt :
>> > Hi Markus!
>> >
>> > On Mo, 13 Apr 2015, Markus Heidelberg wrote:
>> >
>> > [...]
>> >> hg rebase --dest tip~7 --source tip~6 --collapse -m"Add missi
On Di, 14 Apr 2015, Christian Brabandt wrote:
> On Di, 14 Apr 2015, Nikolay Pavlov wrote:
>
> > 2015-04-14 20:45 GMT+03:00 Christian Brabandt :
> > > Hi Markus!
> > >
> > > On Mo, 13 Apr 2015, Markus Heidelberg wrote:
> > >
> > > [...]
> > >> hg rebase --dest tip~7 --source tip~6 --collapse -m"Add
On Di, 14 Apr 2015, Nikolay Pavlov wrote:
> 2015-04-14 20:45 GMT+03:00 Christian Brabandt :
> > Hi Markus!
> >
> > On Mo, 13 Apr 2015, Markus Heidelberg wrote:
> >
> > [...]
> >> hg rebase --dest tip~7 --source tip~6 --collapse -m"Add missing tags"
> >
> > I was brave and tested your script. There
2015-04-14 20:45 GMT+03:00 Christian Brabandt :
> Hi Markus!
>
> On Mo, 13 Apr 2015, Markus Heidelberg wrote:
>
> [...]
>> hg rebase --dest tip~7 --source tip~6 --collapse -m"Add missing tags"
>
> I was brave and tested your script. There are two points I noticed.
> 1) rebase needs to be enabled ex
Hi Markus!
On Mo, 13 Apr 2015, Markus Heidelberg wrote:
[...]
> hg rebase --dest tip~7 --source tip~6 --collapse -m"Add missing tags"
I was brave and tested your script. There are two points I noticed.
1) rebase needs to be enabled explicitly in your .hg/hgrc
2) hg rebase does not seem to unders
2015-04-14 17:37 GMT+03:00 Roland Eggner :
> On 2015-04-13 Monday at 20:00 +0200 Christian Brabandt wrote:
>> On Mo, 13 Apr 2015, Bram Moolenaar wrote:
>> > Markus Heidelberg wrote:
>> > > > Some things can perhaps be done on the Mercurial repository before the
>> > > > import, but I suppose some a
On 2015-04-13 Monday at 20:00 +0200 Christian Brabandt wrote:
> On Mo, 13 Apr 2015, Bram Moolenaar wrote:
> > Markus Heidelberg wrote:
> > > > Some things can perhaps be done on the Mercurial repository before the
> > > > import, but I suppose some are only possible in git. What will happen
> > >
On Mo, 13 Apr 2015, Bram Moolenaar wrote:
> Markus Heidelberg wrote:
> > Hello Bram,
> > currently I'm pretty busy aside from computer, so it all takes a while.
> > But here it is, the first part of cleanup in HG. A Git cleanup process
> > will follow after having finished this step.
> >
> > Am M
Markus Heidelberg wrote:
> Hello Bram,
>
> currently I'm pretty busy aside from computer, so it all takes a while.
> But here it is, the first part of cleanup in HG. A Git cleanup process
> will follow after having finished this step.
>
> Am Mittwoch, 1. April 2015, 21:52:41 schrieb Bram Moolen
ifferences in branches, tags and publishing compared to
Git.
To avoid breaking the HG repo/mirror, cleanup requiring history rewrite
has to be restricted to the Git repo.
Below the script, it is completely non-interactive:
#!/bin/sh
# Vim HG repository cleanup
# close stale branches, switch ba
1 - 100 din 109 matches
Mail list logo
