Evgeny Goldin | 7 Feb 17:43 2012
Picon

Seeing pre-branch history in Hg branch

Hi,


Following these steps to convert SVN branches to Mercurial I see they only contain a post-branch history and do not contain any pre-branch history from SVN trunk. This eventually makes them unrelated when coming to new Mercurial repos which makes merging more of a pain (every branch commit becomes a manual merge).

Where do you think was trunk history omitted from the branch: "svnsycn sync" or "hg clone"? And can it be brought back? 
Thanks!

--
You received this message because you are subscribed to the Google Groups "hgsubversion" group.
To view this discussion on the web visit https://groups.google.com/d/msg/hgsubversion/-/Y88zWzZyLAAJ.
To post to this group, send email to hgsubversion-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To unsubscribe from this group, send email to hgsubversion+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/hgsubversion?hl=en.
Augie Fackler | 8 Feb 15:31 2012
Picon

Re: Seeing pre-branch history in Hg branch


On Feb 7, 2012, at 10:43 AM, Evgeny Goldin wrote:

> Hi,
> 
> Following these steps <http://goo.gl/lEZm9> to convert SVN *branches* to 
> Mercurial I see they only contain a post-branch history and do not contain 
> any pre-branch history from SVN trunk. This eventually makes them unrelated 
> when coming to new Mercurial repos which makes merging more of a pain 
> (every branch commit becomes a manual merge).
> 
> Where do you think was trunk history omitted from the branch: "svnsycn 
> sync" or "hg clone"? And can it be brought back? 

Definitely the hg clone.

Without being able to examine your repository, it's basically impossible to know what's wrong, but it's
highly likely that your branches are created in some unusual way (not a copy of the whole trunk folder?)
that causes hgsubversion to think that they're not actually related to trunk. Are you using 'hg clone' at
the level above branches/tags/trunk or are you cloning each branch one at a time?

> Thanks!
> 
> -- 
> You received this message because you are subscribed to the Google Groups "hgsubversion" group.
> To view this discussion on the web visit https://groups.google.com/d/msg/hgsubversion/-/Y88zWzZyLAAJ.
> To post to this group, send email to hgsubversion@...
> To unsubscribe from this group, send email to hgsubversion+unsubscribe <at> googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/hgsubversion?hl=en.
> 

--

-- 
You received this message because you are subscribed to the Google Groups "hgsubversion" group.
To post to this group, send email to hgsubversion@...
To unsubscribe from this group, send email to hgsubversion+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/hgsubversion?hl=en.

Evgeny Goldin | 12 Feb 11:11 2012
Picon

Re: Seeing pre-branch history in Hg branch

Thanks, Auigie. You're right about branches being created on sub-trunk parts such as "trunk/projectA", "trunk/projectB", etc. Consequently that's what was mirrored with "svnsync" and later "hg clone"-ed.

--
You received this message because you are subscribed to the Google Groups "hgsubversion" group.
To view this discussion on the web visit https://groups.google.com/d/msg/hgsubversion/-/lhPAsEXHK_MJ.
To post to this group, send email to hgsubversion-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To unsubscribe from this group, send email to hgsubversion+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
For more options, visit this group at http://groups.google.com/group/hgsubversion?hl=en.
Evgeny Goldin | 12 Feb 11:12 2012
Picon

Re: Seeing pre-branch history in Hg branch

I mean, yes - each branch was mirrored and cloned separately.

--
You received this message because you are subscribed to the Google Groups "hgsubversion" group.
To view this discussion on the web visit https://groups.google.com/d/msg/hgsubversion/-/FX3zyp59cGYJ.
To post to this group, send email to hgsubversion-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To unsubscribe from this group, send email to hgsubversion+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
For more options, visit this group at http://groups.google.com/group/hgsubversion?hl=en.
Augie Fackler | 13 Feb 15:10 2012
Picon

Re: HgSubversion issue

(+hgsubversion list, for posterity and potential better ideas than my own)

On Feb 13, 2012, at 2:34 AM, Gianluca Romanin wrote:

> Hi Augie,
> I'm a software engineer (from Vimar, Italy : http://www.vimar.eu ) and  I'm
> currently bothering you for a little issue on HgSubversion.
> I haven't posted a bug, because this is not a real bug.
> 
> I'm trying to use a SVN repo server with HgSubversion but hg exits with
> "Out of memory" error and it is not possible to finish the hg pull
> correctly.
> The reason is a bad revision in the SVN repo : in a certain revision
> someone has committed its files and the whole repository again (so in a
> branch I can see
> a full recursion of trunk branch tags etc...). This error produces a lot of
> files to parse for HgSubversion in a single checkout and it runs out of
> memory because, for what I can imagine,
> all the files are stored in RAM memory. I can't operate on the SVN repo to
> correct the revision, supposing this is feasible. The repo is from a closed
> source product out of my boundaries.
> The same thing can be imported, after several hours, with git-svn, which
> uses the native svn checkout (for what I can see). Git is incredibly slower
> than Hg with SVN!
> 
> Do you have any suggestion to bypass this problem?
> It is possible to implement something in HgSubversion to use filesystem
> instead of RAM for temp SVN checkout?

It actually used to do this, in the mists of time. 

Anyway, you should be able to make this work by modifying HgEditor to use a disk-backed dict instead of an
in-memory dict, or alternatively try a 64 bit build of Python (assuming your system can handle it). I'm
afraid I can't commit to even making an attempt at doing this for you anytime soon, as my plate is already
quite full.

> Thank you for your time!
> Buona giornata,
> 
> ------------------------------------------------------
> Gianluca Romanin (aka J_Zar)
> ------------------------------------------------------
> Skype : romaninz
> GTalk  : romaninz@...
> ------------------------------------------------------

--

-- 
You received this message because you are subscribed to the Google Groups "hgsubversion" group.
To post to this group, send email to hgsubversion@...
To unsubscribe from this group, send email to hgsubversion+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/hgsubversion?hl=en.

Kanaan Venkateswaran | 16 Feb 18:05 2012

preserve author names

Is there a way to preserve author name after pushing to svn? I
couldn't find a definitive answer to it.
currently all the developer's changes are checked in svn under my name
and then it pulls changeset back and loses original author name.
Thanks
Kannan

--

-- 
You received this message because you are subscribed to the Google Groups "hgsubversion" group.
To post to this group, send email to hgsubversion@...
To unsubscribe from this group, send email to hgsubversion+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hgsubversion?hl=en.

Cesar Izurieta | 16 Feb 18:26 2012

Re: preserve author names

There are some patches that I submitted to this mailing list some time ago. You may find them in the mailing list achives. They set a hg:author revprop that is reconstructed when checking out from subversion.

On Thu, Feb 16, 2012 at 12:05 PM, Kanaan Venkateswaran <kvenkateswaran-6vG9JQab4o/QFizaE/u3fw@public.gmane.orgm> wrote:
Is there a way to preserve author name after pushing to svn? I
couldn't find a definitive answer to it.
currently all the developer's changes are checked in svn under my name
and then it pulls changeset back and loses original author name.
Thanks
Kannan

--
You received this message because you are subscribed to the Google Groups "hgsubversion" group.
To post to this group, send email to hgsubversion-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To unsubscribe from this group, send email to hgsubversion+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
For more options, visit this group at http://groups.google.com/group/hgsubversion?hl=en.


--
You received this message because you are subscribed to the Google Groups "hgsubversion" group.
To post to this group, send email to hgsubversion-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To unsubscribe from this group, send email to hgsubversion+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/hgsubversion?hl=en.
Augie Fackler | 17 Feb 21:25 2012
Picon

Re: preserve author names

On Thu, Feb 16, 2012 at 11:05 AM, Kanaan Venkateswaran
<kvenkateswaran@...> wrote:
> Is there a way to preserve author name after pushing to svn? I
> couldn't find a definitive answer to it.
> currently all the developer's changes are checked in svn under my name
> and then it pulls changeset back and loses original author name.

Not really, it's a limitation of the Subversion protocol. If you
wanted, you could do a post-commit svn propedit of the revprops (after
configuring a revprop edit hook, without which the operation will be
rejected), but it's not something I've ever supported because it's a
really unusual request.

> Thanks
> Kannan
>
> --
> You received this message because you are subscribed to the Google Groups "hgsubversion" group.
> To post to this group, send email to hgsubversion@...
> To unsubscribe from this group, send email to hgsubversion+unsubscribe@...
> For more options, visit this group at http://groups.google.com/group/hgsubversion?hl=en.
>

--

-- 
You received this message because you are subscribed to the Google Groups "hgsubversion" group.
To post to this group, send email to hgsubversion@...
To unsubscribe from this group, send email to hgsubversion+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hgsubversion?hl=en.

hgsubversion | 25 Feb 21:58 2012

3 new revisions pushed by durin42 on 2012-02-25 20:58 GMT

3 new revisions:

Revision: 4e43e30e3e7d
Author:   Will Wykeham <will@...>
Date:     Fri Aug 12 16:41:08 2011
Log:      Support non-standard tunnels...
http://code.google.com/p/hgsubversion/source/detail?r=4e43e30e3e7d

Revision: d3bc067c0f72
Author:   Will Wykeham <will@...>
Date:     Tue Aug 16 04:39:42 2011
Log:      Cope with non standard schemes in externals
http://code.google.com/p/hgsubversion/source/detail?r=d3bc067c0f72

Revision: 9ce00cb1d676
Author:   Augie Fackler <durin42@...>
Date:     Sat Feb 25 12:51:22 2012
Log:      Merge alternate tunnel schemes.
http://code.google.com/p/hgsubversion/source/detail?r=9ce00cb1d676

==============================================================================
Revision: 4e43e30e3e7d
Author:   Will Wykeham <will@...>
Date:     Fri Aug 12 16:41:08 2011
Log:      Support non-standard tunnels

Ideally we'd just specify some form of wildcard svn+* pattern, but that  
isn't possible
without patching mercurial itself as well, so we'll just specify tunnels  
individually
http://code.google.com/p/hgsubversion/source/detail?r=4e43e30e3e7d

Modified:
  /hgsubversion/__init__.py

==============================================================================
Revision: d3bc067c0f72
Author:   Will Wykeham <will@...>
Date:     Tue Aug 16 04:39:42 2011
Log:      Cope with non standard schemes in externals
http://code.google.com/p/hgsubversion/source/detail?r=d3bc067c0f72

Modified:
  /hgsubversion/svnexternals.py

==============================================================================
Revision: 9ce00cb1d676
Author:   Augie Fackler <durin42@...>
Date:     Sat Feb 25 12:51:22 2012
Log:      Merge alternate tunnel schemes.
http://code.google.com/p/hgsubversion/source/detail?r=9ce00cb1d676

Modified:
  /hgsubversion/svnexternals.py

--

-- 
You received this message because you are subscribed to the Google Groups "hgsubversion" group.
To post to this group, send email to hgsubversion@...
To unsubscribe from this group, send email to hgsubversion+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hgsubversion?hl=en.

hgsubversion | 3 Mar 00:37 2012

push by durin42 - Include documentation in tarballs (fixes #317). on 2012-03-02 23:36 GMT

Revision: 8a226f0f99aa
Author:   Dirkjan Ochtman <dirkjan@...>
Date:     Thu Mar  1 04:28:18 2012
Log:      Include documentation in tarballs (fixes #317).
http://code.google.com/p/hgsubversion/source/detail?r=8a226f0f99aa

Modified:
  /MANIFEST.in

--

-- 
You received this message because you are subscribed to the Google Groups "hgsubversion" group.
To post to this group, send email to hgsubversion@...
To unsubscribe from this group, send email to hgsubversion+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hgsubversion?hl=en.


Gmane