> I am not sure where to request feature additions:
>
> 1) I would like to have the output of repoutil list the branches in sort order.
>
> It is hard to find the branch in a see of branches. This is what I currently get:
> 041-4057 Remote Desktop Client Update 3.5.2 2012-02-01 ['Theatre-Release', 'KAM-Release', 'KCPA-Release', 'ArtDesignMng-Release', 'VRC-Release', 'PublicAffairs-Release', 'KCPA-Testing']
>
> I would like something like:
> 041-4057 Remote Desktop Client Update 3.5.2 2012-02-01 ['ArtDesignMng-Release', 'KAM-Release', 'KCPA-Release', 'KCPA-Testing', 'Theatre-Release', 'PublicAffairs-Release', 'VRC-Release' ]
>
>
> 2) When running a repoutil ----list-branch=<branchname> can we have an option to not show the branches?
> ie:
> 041-4057 Remote Desktop Client Update 3.5.2 2012-02-01
>
> 3) Any chance of getting any thing that will compare branches. For instance: repoutil -diff KCPA-Testing KCPA-Release
repoutil --list-branch foo > foo.txt
repoutil --list-branch bar > bar.txt
diff foo.txt bar.txt
As for the others, if someone wants to contribute patches, I will consider them.
(I do wonder why you need quite so many branches. I can see how managing so many would be difficult. But if you want to ensure two branches are the same, --copy-branch might be of use...)
-Greg
Thanks.
The reason for so many branches is that we are supporting 13 different units with 13 different IT Support people and policies. We are just now reorganizing ourselves to manage these from a central IT structure. However, each unit has there own needs and software. There is a general concern that "patch A" will break something that only 1 or 2 units need. We should not keep the other units from updating though. It gives us the most flexibility and the most headaches. Also, its important that the labs be updated at only specific times.
As we learn each of the units, I hope to bring them back into only a few branches that can be shared. Until then, I am enjoying the nightmare.