git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Petr Baudis <pasky@suse.cz>
To: James Cloos <cloos+vger-git@jhcloos.com>
Cc: git@vger.kernel.org, Darrin Thompson <darrint@progeny.com>
Subject: Re: cg update failing
Date: Wed, 20 Jul 2005 10:12:26 +0200	[thread overview]
Message-ID: <20050720081226.GA27102@pasky.ji.cz> (raw)
In-Reply-To: <m3oe8yw0ws.fsf@lugabout.cloos.reno.nv.us>

Dear diary, on Wed, Jul 20, 2005 at 06:34:43AM CEST, I got a letter
where James Cloos <cloos+vger-git@jhcloos.com> told me that...
> >>>>> "Petr" == Petr Baudis <pasky@suse.cz> writes:
> 
> Petr> Huh. Well, you had to do uberweird things with your repository -
> Petr> why did you cg-seek at all? What Cogito version is it?
> 
> All I ever did was track and compile linus??? tree.  IIRC, when the
> first new tag was added after I cloned the tree I had to seek to
> that tag to see the new versions of the files.  But obviously
> that was long enough before hg???s repo broke that I???d forgotten
> how I???d done that....

Ah so. Well, yes, the first tag was IIRC weird since it was a tree tag,
not a commit tag. That confused things, but it shouldn't be necessary
anymore since all new tags are hopefully commits. That might somehow
create the local modifications as well, although I don't have a clear
idea how could be that possible. Well, there were some bugs like this in
Cogito in the past, but that should be long fixed.

Thanks anyway,

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
If you want the holes in your knowledge showing up try teaching
someone.  -- Alan Cox

      reply	other threads:[~2005-07-20  8:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-14 18:04 cg update failing James Cloos
2005-07-14 18:24 ` Darrin Thompson
2005-07-14 20:06   ` James Cloos
2005-07-14 21:21     ` Darrin Thompson
2005-07-14 21:50       ` James Cloos
2005-07-15  4:12         ` James Cloos
2005-07-20  1:07           ` Petr Baudis
2005-07-20  4:34             ` James Cloos
2005-07-20  8:12               ` Petr Baudis [this message]

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=20050720081226.GA27102@pasky.ji.cz \
    --to=pasky@suse.cz \
    --cc=cloos+vger-git@jhcloos.com \
    --cc=darrint@progeny.com \
    --cc=git@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).