Matthias Klose <[EMAIL PROTECTED]> writes: >> * there is no branch for those patches that are intended for etch; > > yes, create one, maybe based on the gcc-4.1-4.1.1ds2-20 tag.
OK, I'll branch "etch" off of that and start integrating the patch. >> * and last month you said you didn't want me to create such a branch. > > no, I did not want to rename the sid branch to experimental, or create > a new experimental branch. we surely can rename sid to trunk, and not > using branches/sid at all. Well, at this time we do need at least two branches since some of our patches are intended for etch, and some others aren't. I think we should use /trunk and /branches/etch; that's the Subversion convention. Also, the subdirectories "/tags/sid" and "/tags/woody" should go away altogether, and their contents be moved up one directory. >> If you don't want me to branch, then I will not try to apply the >> patch; I will wait until etch is released and the Subversion >> repository is in a sane state again (i.e the sid branch builds on sid, >> and is the branch that gets uploaded to unstable). > > as you like it. The way I like it is by branching and merging :) Since you approved, I'll go ahead now. -- Ludovic Brenta. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]