This is the mail archive of the
mailing list for the glibc project.
Re: follow-up on tile architecture changes
> Should this be one branch per change? Or should I queue a number of
> changes into one branch that I can use for staging all my core changes,
> e.g., "cmetcalf/tile/"?
If the changes are not directly interdependent, then one branch per change
is easier for selective merging. (Of course, you can structure the names
of the branches however you like, e.g. putting them all under cmetcalf/tile/.)