after stg commit all patch history is loss. It's sucks. there are nothing lost in bzr loom .
\\wbr Vitaly Chernookiy
after stg commit all patch history is loss. It's sucks. there are nothing lost in bzr loom .
\\wbr Vitaly Chernookiy
Re: Fwd: Bug in StackedGit
On 2008-04-15 10:06:43 +0000, Vitaly V. Ch wrote:
> after stg commit all patch history is loss. It's sucks. there are > nothing lost in bzr loom .
I assume you refer to the patch history shown by "stg log"?
I'm working on a new and improved patch log/undo thingy for StGit, which doesn't lose the history of your patches when they are deleted. Thanks to constructive feedback such as this, it'll be completed in no time. ;-)
--
Karl Hasselström, kha@treskal.com
www.treskal.com/kalleRe: Fwd: Bug in StackedGit
On Tue, Apr 15, 2008 at 10:38 AM, Karl Hasselström <kha@treskal.com> wrote:
> On 2008-04-15 10:06:43 +0000, Vitaly V. Ch wrote: > > > after stg commit all patch history is loss. It's sucks. there are > > nothing lost in bzr loom . > > I assume you refer to the patch history shown by "stg log"?
Yes. There are sometimes sens to revert some patch after commit to previous version.
\\wbr Vitaly Chernookiy
> > I'm working on a new and improved patch log/undo thingy for StGit, > which doesn't lose the history of your patches when they are deleted. > Thanks to constructive feedback such as this, it'll be completed in no > time. ;-) > > -- > Karl Hasselström, kha@treskal.com > www.treskal.com/kalle >
Re: Fwd: Bug in StackedGit
On 2008-04-15 10:46:38 +0000, Vitaly V. Ch wrote:
> On Tue, Apr 15, 2008 at 10:38 AM, Karl Hasselström <kha@treskal.com> > wrote: > > > On 2008-04-15 10:06:43 +0000, Vitaly V. Ch wrote: > > > > > after stg commit all patch history is loss. It's sucks. there > > > are nothing lost in bzr loom . > > > > I assume you refer to the patch history shown by "stg log"? > > Yes. There are sometimes sens to revert some patch after commit to > previous version.
That use case (resetting a single patch to any previous version, even if the patch has since been committed or deleted) is handled (albeit in a somewhat unpolished form) by the code in my experimental branch since about 12 hours ago. Just in time. :-)
--
Karl Hasselström, kha@treskal.com
www.treskal.com/kalleRe: Bug in StackedGit
On 15/04/2008, Vitaly V. Ch <vitaly.v.ch@gmail.com> wrote:
> after stg commit all patch history is loss. It's sucks.
Why do you need the patch history after "stg commit"? This command is meant to take the patches out of StGIT control and freeze them in the Git repository history.
-- Catalin
Re: Bug in StackedGit
I want revert some patch to one of previous version like I can do same in bzr loom.
\\wbr Vitaly Chernookiy
On Tue, Apr 15, 2008 at 11:13 AM, Catalin Marinas <catalin.marinas@gmail.com> wrote:
> On 15/04/2008, Vitaly V. Ch <vitaly.v.ch@gmail.com> wrote: > > after stg commit all patch history is loss. It's sucks. > > Why do you need the patch history after "stg commit"? This command is > meant to take the patches out of StGIT control and freeze them in the > Git repository history. > > -- > Catalin >