From: James Cloos <cloos+vger-git@jhcloos.com>
To: git@vger.kernel.org
Cc: Darrin Thompson <darrint@progeny.com>
Subject: Re: cg update failing
Date: Fri, 15 Jul 2005 00:12:48 -0400 [thread overview]
Message-ID: <m3eka04shr.fsf@lugabout.cloos.reno.nv.us> (raw)
In-Reply-To: <m3d5plm50o.fsf@lugabout.cloos.reno.nv.us> (James Cloos's message of "Thu, 14 Jul 2005 17:50:15 -0400")
Well, it wasn't as Ok as I first thought. There were several .rej and
backup files as left behind by patch(1). cg update HEAD says: Branch
already fully merged but Makefile still says 2.6.12.
I'm cloning now to a remote uml and will try and rsync from there to
the laptop. Perhaps *that* will get me a working repo.
[SIGH]
-JimC
next prev parent reply other threads:[~2005-07-15 4:13 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 [this message]
2005-07-20 1:07 ` Petr Baudis
2005-07-20 4:34 ` James Cloos
2005-07-20 8:12 ` Petr Baudis
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=m3eka04shr.fsf@lugabout.cloos.reno.nv.us \
--to=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).