Re: [RFC] Adding stack-level logging/undo to StGIT

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

 



On 05/01/07, Yann Dirson <ydirson@xxxxxxxxxx> wrote:
This mail is a draft collection of design ideas to hopefully progress
towards full "undo" functionnality in StGIT.  The issue is not
trivial, so I'd prefer to hear from users before starting to code
anything :)

(couldn't finish reading all the e-mail, too long :-) and I'm too tired)

The idea of transactions and unified undo/redo is very good but it's a
bit more complicated with the current structure, which I admit isn't a
good design (too many files and metadata; I initially started StGIT as
shell script prototype and moved to Python without re-designing the
structure). Ideally, we would have the full stack state in a single
file that could be stored as git object and get unlimited undo
facilities or history tracking.

But this is part of a post 1.0 development. I plan to fix some of the
outstanding issues (still need to create the TODO wiki page) and go
towards a first 1.0 release candidate (and release 1.0 sometime this
spring). I think StGIT now has most of the features I initially
planned for 1.0. After that we can re-design the current structure and
make it simpler to support transactions and full history for both
patches and the stack as a whole.

--
Catalin
-
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]