From: Petr Baudis <pasky@suse.cz>
To: Russell King <rmk@arm.linux.org.uk>
Cc: git@vger.kernel.org
Subject: Re: Local cg-pull fails
Date: Sat, 23 Jul 2005 01:22:19 +0200 [thread overview]
Message-ID: <20050722232218.GO11916@pasky.ji.cz> (raw)
In-Reply-To: <20050714111224.B31383@flint.arm.linux.org.uk>
Dear diary, on Thu, Jul 14, 2005 at 12:12:25PM CEST, I got a letter
where Russell King <rmk@arm.linux.org.uk> told me that...
> Last time this was discussed, someone suggested -f, which solved the
> problem. Can we please modify the cg-pull script to use -f ?
Thanks, done.
> Secondly, can I suggest that cogito developers consider the above
> usage scenario and construct a regression test for it to ensure that
> future breakages of this nature are caught. For me, cogito has been
> extremely fragile, and I don't think the above usage is unreasonable.
Done.
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
If you want the holes in your knowledge showing up try teaching
someone. -- Alan Cox
prev parent reply other threads:[~2005-07-22 23:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-14 10:12 Local cg-pull fails Russell King
2005-07-22 23:22 ` 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=20050722232218.GO11916@pasky.ji.cz \
--to=pasky@suse.cz \
--cc=git@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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).