>> Can you describe a scenario where this is desired behaviour?

Yes, for example, let's say I have a base repository for an Office Suite:

Office_Repository: Math libs, Style libs, Menu system, etc...

And then I have branches for
    +---Calc app,
    +---Write app,
    +---BD App

 wich use the common libs from Repository and also each of them have their own utilities, so what I'm looking for is a way to for example, fix a bug in "Math lib" from Calc App. and push this fix into de Base respository, but not pushing to the repository the rest of particular utilities for Calc App.

Anyway, what you told me is appropiatte for me now, I can copy the fixed libraries and then pull them from the other branches. In the link you sent me I saw this <a href"http://www.selenic.com/mercurial/wiki/index.cgi/ForestExtension">Forest extension</a>, I will read about it, maybe it's what I need

Thank you
(I send again, sorry I didn't reply all)

Peer Sommerlund escribió:

2008/11/11 Krilin <[EMAIL PROTECTED]>
Hello, I'm new with Tortoise (under Windows) and new in the list, so I'm not really sure this is the place to post this... Apoligizes if this is not the place.

Well, it turns out that your question probably should have been on the mercurial list, but let me see if I can answer you.


It's the first time I use a CVS and so far I managed to create a repository and create clones, but now I would like to create branches from a repository, this is, from a repository to have two or more clones, but this clones can grow with different files, so:

Repository: Files A, B
   +----- Branch 1: Files A, B, F1
   +----- Branch 2: Files A, B, F2

And when I modify file A or B in any of the branches they can be pushed in the repository, but never files F1 or F2 be pushed.

Can you describe a scenario where this is desired behaviour?

Usual configuration is to have something like
- stable_repo: A, B
- unstable_repo: A, B, F1, F2
where F1 and F2 are new files with interesting features
bugfixes would be made to stable_repo and then pulled to unstable_repo

The situation you describe could be handled with the mq extension and branches on the patch repository - but since you are new to version control systems I think you should try something simpler to start with.

A good starting point is
http://www.selenic.com/mercurial/wiki/index.cgi/UnderstandingMercurial

Regards,
Peer
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Tortoisehg-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss

Reply via email to