What is our preferred gitorious workflow wrt merges and pushes?
aleixpol at kde.org
Sun Oct 10 21:09:10 UTC 2010
On Sun, Oct 10, 2010 at 5:32 PM, Alexander Dymo <alexander.dymo at gmail.com>wrote:
> On 10.10.10 15:55:49, Alexander Dymo wrote:
>> You mean merge your branches into kdevelop/master and then push that,
>> right? So far thats what we've done, i.e. no need to specifically rebase
>> a branch against 'current' master to get a linear history.
> Yeah, that was basically my question, do we care about linearity of our
> Looks like we don't (and git log --graph --all also suggests that we
> IMHO linear history is much simpler to understand, but it does introduce
> some specifics wrt personal
> gitorious clone management (like I shown in example A1).
> For my own repos I usually try to keep history linear where possible.
> KDevelop-devel mailing list
> KDevelop-devel at kdevelop.org
I thing linear history is better but also harder to maintain personally. I
think the best would be to recommend to use rebase but not force anything.
rebase can lead to problems anyway, I once used it and it duplicated a ton
of commits -.-. (Probably I did it wrong, but merging never goes wrong :)
It's also quite ugly to see all the merge commits in git log.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the KDevelop-devel