"Daniel 'NebuchadnezzaR' Dehennin" <[EMAIL PROTECTED]>
writes:
> Le 4688 Septembre 1993, Stefan Reichör a tapoté:
>
>> What features would you like to see at least to start using the
>> bookmark functionality?
>
> Firstly, the possibility to define partners and to check missing
> patches from them.
For this also, we should check with the development team of the
various tools whether there can be something in the tool about that.
bzr already keeps track of upstream when you branch (so missing and
pull will not need the URL), but the other way is AFAIK missing. I'd
represent the typical star-shaped situation as follows :
upstream
/ ^ \
/ | \
... You ...
/ | \
/ | \
... ... ...
people
who contribute
through you
On small project, there is usually only one step, so you're either
topmost or leaf of the tree, but on larger ones, some people will
integrate sets of related patches before submitting them to upstream
(I think this is mostly how the things happen for the Linux kernel).
So, bzr provides the information for the way up, but not the way down.
For Xtla, we had redundant information : the per-user information
stored in Xtla-specific format in the bookmarks, and the per-branch in
{arch}/=partner-version. The problem is that the
{arch}/=partner-version was only used by us (Xtla) and aba (bash
wrapper for tla), so a convention between only two front-ends wasn't
terribly useful.
--
Matthieu
_______________________________________________
Dvc-dev mailing list
[email protected]
https://mail.gna.org/listinfo/dvc-dev
