[GSoC update] Sequencer: Dealing with historical mistakes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

Junio suddenly raised some very disturbing concerns about the overall
UI consistency wrt '--continue'.  I'm really glad he raised it before
we locked ourselves into yet another UI mistake.  Work on the
generalized sequencer series has totally halted since, and I've been
pondering about what to do.  After some thought, I've tried to
untangle the various issues and add something useful to the discussion
[1].  I'm somewhat annoyed that we're stuck with these historical
mistakes, and I hope that our future design isn't constrained too
badly.

Otherwise, I've requested Junio to merge 'rr/cherry-pick-continue'
as-it-is, since it doesn't have any major issues.  The generalized
sequencer series itself will take some more time- we have to decide
the final implementation details at the end of the discussion.  Also,
the GSoC is drawing to a close, and I plan to post a somewhat
elaborate final update.  If there's something in particular you'd like
to see in it, do let me know.

Thanks for reading.

[1]: http://mid.gmane.org/CALkWK0noHBnW-7zZLw=jJdDVFxXmsm2vHHYnUJc9miLLuDRnAg@xxxxxxxxxxxxxx

-- Ram
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]