Tristan Seligmann wrote:
So how do the darcs developers (or other darcs users) handle this? When
you are working on some feature for darcs that takes a while and
involves many patches what do you do when you want to roll it into the
release tree?
If I'm working on multiple features at the same time that need to be
merged separately, I'll do it in separate repos so that each repo only
has changes relating to one particular feature.
Right. I do that as well but lets say feature X is a bit involved and
takes 3 days to do it with a couple of revs to get right. During that
time say you have generated 10 patches each with its own subparts of the
feature.
Do this 3 times. So now you have 30 new patches pushed out to the repo.
Other people pull all of them but eventually you think that feature 2
still has some problems. Sorting out what patches for other to unpull
can be somewhat confusing. Especially if its been a month since you
wrote those patches.
I understand that this is mostly logistics. Ie. having good patch names,
descriptions, and tagging but I was wondering if darcs could help with
that any by logically grouping the patches.
--
Richard A. Smith
Bitworks, Inc
_______________________________________________
darcs-users mailing list
[email protected]
http://www.abridgegame.org/mailman/listinfo/darcs-users
