All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: "Karl Hasselström" <kha@treskal.com>
Cc: git@vger.kernel.org, Catalin Marinas <catalin.marinas@gmail.com>,
	Yann Dirson <ydirson@altern.org>
Subject: Re: 'pu' branch for StGIT
Date: Thu, 09 Aug 2007 12:33:30 -0400	[thread overview]
Message-ID: <1186677210.31394.28.camel@dv> (raw)
In-Reply-To: <20070809141848.GA6342@diana.vm.bytemark.co.uk>

On Thu, 2007-08-09 at 16:18 +0200, Karl Hasselström wrote:

> You should be able to do something like
> 
>   $ stg applied > .git/patches/branch/applied
>   $ stg unapplied > .git/patches/branch/unapplied
> 
> and then manually change the version from 3 to 2, and be ready to go.
> I haven't tested this, though!

That seems to work.  Thank you!  "branch" should be substituted with the
current branch, of course.

> > I have noticed two problems so far, but I cannot tell is they are
> > specific to the "pu" branch.
> >
> > 1) Undead patches.
> 
> I saw the same problem today. I haven't had time to look into it, but
> I believe it's due to stgit trying to directly modify files under
> .git/refs instead of using git-update-ref, which breaks with packed
> refs. The DAG patches rely much more on the refs, so the bug is more
> severe in that case.
> 
> https://gna.org/bugs/?9710

I've attached the test case to that bug.  You are right, git-gc is involved.

> > 2) Invisible branches.
> 
> I haven't seen this problem at all -- in my repositories, "stg branch
> -l" just works. Will try to reproduce (hopefully tonight). Do you have
> a recepie on how to reproduce this from scratch?

It's a problem with git-gc too!  Just clone some repository and run "stg
branch -l" in it.  It with show master.  Run git-gc, and "stg branch -l"
will show "No branches".

I see that in my Linux repository there are files
in .git/refs/remotes/wireless-dev but not in other directories
under .git/refs/remotes/

-- 
Regards,
Pavel Roskin

  parent reply	other threads:[~2007-08-09 16:34 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-07  2:20 'pu' branch for StGIT Karl Hasselström
2007-08-07  2:38 ` Shawn O. Pearce
2007-08-08  5:03 ` Pavel Roskin
2007-08-08  9:20   ` Karl Hasselström
2007-08-08 21:39     ` Karl Hasselström
2007-08-08 22:18       ` Pavel Roskin
2007-08-08 23:23         ` Karl Hasselström
2007-08-09  0:10           ` Pavel Roskin
2007-08-09  7:38             ` Karl Hasselström
2007-08-09 13:24               ` Pavel Roskin
2007-08-09 14:18                 ` Karl Hasselström
2007-08-09 14:24                   ` Karl Hasselström
2007-08-09 16:33                   ` Pavel Roskin [this message]
2007-08-09 20:39                     ` Karl Hasselström
2007-08-10  3:23                       ` [StGIT PATCH 0/2] Teach StGIT to survive git-gc Karl Hasselström
2007-08-10  3:23                         ` [StGIT PATCH 1/2] New test: make sure that StGIT can handle packed refs Karl Hasselström
2007-08-10  3:23                         ` [StGIT PATCH 2/2] Don't touch ref files manually Karl Hasselström
2007-08-21 13:23                           ` Catalin Marinas
2007-08-21 15:58                             ` Karl Hasselström
2007-08-21 16:09                               ` Karl Hasselström
2007-08-21 16:12                               ` Johannes Sixt
2007-08-21 16:38                                 ` Karl Hasselström
2007-08-21 16:46                             ` Karl Hasselström
2007-08-21 20:48                               ` Karl Hasselström
2007-08-23 14:04                               ` Catalin Marinas
2007-08-09 21:31                 ` 'pu' branch for StGIT Catalin Marinas
2007-08-10  0:30                   ` Karl Hasselström
2007-08-12 22:47                   ` Pavel Roskin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1186677210.31394.28.camel@dv \
    --to=proski@gnu.org \
    --cc=catalin.marinas@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=kha@treskal.com \
    --cc=ydirson@altern.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.