From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: martin f krafft <madduck@madduck.net>
Cc: Aneesh Kumar <aneesh.kumar@gmail.com>, git@vger.kernel.org
Subject: Re: [topgit] tg update error
Date: Thu, 12 Feb 2009 15:42:43 +0530 [thread overview]
Message-ID: <20090212101243.GC21074@skywalker> (raw)
In-Reply-To: <20090212093227.GC20248@piper.oerlikon.madduck.net>
On Thu, Feb 12, 2009 at 10:32:27AM +0100, martin f krafft wrote:
> also sprach Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com> [2009.02.12.1025 +0100]:
> > Latest git and topgit. Moving to git version v1.6.1.3 fixed the issue.
> > I can reproduce the problem on any test repo. Just do a tg update after
> > committing something in the dependent branch.
>
> This is not helpful. Please provide a complete transcript of
> a session reproducing the problem.
>
> I can't:
>
> piper:~/.tmp/cdt.GydvBgiR|test|% git --version #10010
> git version 1.6.0.2
The git version that failed for me is the latest git. As I mentioned
above git version 1.6.1.3 works fine.
Can you test with
$git --version
git version 1.6.2.rc0.55.g30aa4f
-aneesh
next prev parent reply other threads:[~2009-02-12 10:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-12 8:09 [topgit] tg update error Aneesh Kumar
2009-02-12 8:48 ` martin f krafft
2009-02-12 9:25 ` Aneesh Kumar K.V
2009-02-12 9:32 ` martin f krafft
2009-02-12 10:12 ` Aneesh Kumar K.V [this message]
2009-02-12 11:29 ` Bert Wesarg
2009-02-12 12:56 ` Jeff King
2009-02-12 12:59 ` Jeff King
2009-02-12 21:01 ` martin f krafft
2009-02-12 21:01 ` Junio C Hamano
2009-02-12 21:41 ` martin f krafft
2009-02-12 23:14 ` Junio C Hamano
2009-02-13 6:28 ` martin f krafft
2009-02-13 7:32 ` Junio C Hamano
2009-02-13 9:04 ` Junio C Hamano
2009-02-13 18:26 ` Jeff King
2009-02-14 2:02 ` Junio C Hamano
2009-02-14 2:08 ` Jeff King
2009-02-14 2:16 ` Junio C Hamano
2009-02-14 2:24 ` Jeff King
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=20090212101243.GC21074@skywalker \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=aneesh.kumar@gmail.com \
--cc=git@vger.kernel.org \
--cc=madduck@madduck.net \
/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.