[Chicago] Teach Me <something> at a ChiPy meeting?

Augie Fackler lists at durin42.com
Fri Sep 19 23:23:13 CEST 2008

On Sep 19, 2008, at 4:03 PM, Cosmin Stejerean wrote:

> Pulling a branch into a separate repository is not a problem with any
> of the DVCS solutions, but that is quite different from pulling out a
> folder from a project out into a separate repository just for that
> folder. I'm not aware of any existing solutions, but it should be
> possible to put together a script that examines the commits in order,
> figures out which commits touch only the files you want, creates a
> series of patches that only touch that subfolder then apply all those
> patches in order on to a new repository.

It should be fairly straightforward using either the transplant or  
convert extensions to Mercurial. If you jump on #mercurial on  
irc.freenode.net there will probably be someone that can help. You'll  
have better luck in the mornings, since the author of convert is en  
Europe and tends to be around then.

> -- 
> Cosmin Stejerean
> http://blog.offbytwo.com
> On Fri, Sep 19, 2008 at 11:53 AM, Garrett Smith <g at rrett.us.com>  
> wrote:
>> If it's anything like Bazaar (Mercurial, git, and Bazaar should be  
>> on anyone's short list for a DVCS) you should be able to move (or  
>> push) the branch into its own repository.
>> I do know that this is trivial/endemic behavior with Bazaar.
>> Some propaganda:
>> http://bazaar-vcs.org/BzrVsHg
>> I recently researched the three tool sets and have adopted Bazaar,  
>> but, from what I've read, Mercurial is outstanding as well.
>> ----- "Lukasz Szybalski" <szybalski at gmail.com> wrote:
>>> On Thu, Mar 20, 2008 at 12:24 PM, Atul Varma <varmaa at gmail.com>
>>> wrote:
>>>> On Thu, Mar 20, 2008 at 12:14 PM, Martin Maney <maney at two14.net>
>>> wrote:
>>>>> [ot, after noticing the randomly selected sig quote: /me wonders
>>> if
>>>>> Joey's using git now?  I know he has a neat sounding tool to help
>>> with
>>>>> managing your /etc using git that I'd need to find time to play
>>> with.]
>>>> Hey, this can be OT if you use mercurial instead of git. :)  It
>>> would be
>>>> really easy with mercurial, too... I think just do this as root:
>>>>  $ cd /etc
>>>>  $ hg init
>>>>  $ hg add *
>>>>  $ hg commit
>>>> o yea.
>>> quick question. Is mercurial able to keep a revision history for  
>>> each
>>> folder as a separate entity.
>>> I put all my projects under trunk  and then work on each project in
>>> its own folders. Few years laster if one project expends and I need
>>> to
>>> take it out of trunk and put it under its own trunk source control,
>>> is
>>> there an adventage that mercurial could give me vs svn as far as
>>> keeping track of it. Is it easier to seperating one folder out of  
>>> the
>>> whole trunk? I know this is tricky with svn as you need to filter  
>>> the
>>> dump file for revisions that are connected to a folder you want to
>>> export and if you don't have access to make dump file for main trunk
>>> ....then its virtually impossible.
>>> Thanks,
>>> Lucas
> _______________________________________________
> Chicago mailing list
> Chicago at python.org
> http://mail.python.org/mailman/listinfo/chicago

More information about the Chicago mailing list