From: "Sean" <seanlkml@sympatico.ca>
To: "Petr Baudis" <pasky@suse.cz>
Cc: "Jon Loeliger" <jdl@freescale.com>, git@vger.kernel.org
Subject: Re: Please undo "Use git-merge instead of git-resolve in
Date: Thu, 22 Sep 2005 15:25:34 -0400 (EDT) [thread overview]
Message-ID: <BAYC1-PASMTP0510EEC44C7F787F27215AAE970@CEZ.ICE> (raw)
Message-ID: <34462.10.10.10.28.1127417134.squirrel@linux1> (raw)
In-Reply-To: <20050922191058.GM21019@pasky.or.cz>
On Thu, September 22, 2005 3:10 pm, Petr Baudis said:
> FWIW, with Cogito, interrupted or failed fetch can be safely rerun, no
> extra recovery procedure is required. It *seems* that this holds for
> git-fetch as well.
Petr,
Why doesn't cogito just use the git fetch/pull commands? Why does it
need anything special? It seems like cogito is doing more than just
being an ease-of-use layer above git.
Sean
next prev parent reply other threads:[~2005-09-22 19:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-22 18:32 Please undo "Use git-merge instead of git-resolve in Jon Loeliger
2005-09-22 19:10 ` Petr Baudis
[not found] ` <34462.10.10.10.28.1127417134.squirrel@linux1>
2005-09-22 19:25 ` Sean [this message]
2005-09-22 22:22 ` Junio C Hamano
[not found] ` <55917.10.10.10.28.1127429674.squirrel@linux1>
2005-09-22 22:54 ` Sean
2005-09-23 9:10 ` Petr Baudis
2005-09-23 9:34 ` Junio C Hamano
2005-09-23 9:57 ` Petr Baudis
2005-09-23 21:07 ` Daniel Barkalow
2005-09-24 6:19 ` Junio C Hamano
2005-09-22 21:12 ` Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2005-09-23 13:51 Jon Loeliger
2005-09-22 19:12 Jon Loeliger
2005-09-22 21:22 ` Linus Torvalds
2005-09-22 21:37 ` Linus Torvalds
2005-09-22 21:57 ` Daniel Barkalow
2005-09-22 22:05 ` Linus Torvalds
2005-09-22 14:55 Jon Loeliger
2005-09-22 16:01 ` Petr Baudis
2005-09-22 16:06 ` Linus Torvalds
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=BAYC1-PASMTP0510EEC44C7F787F27215AAE970@CEZ.ICE \
--to=seanlkml@sympatico.ca \
--cc=git@vger.kernel.org \
--cc=jdl@freescale.com \
--cc=pasky@suse.cz \
/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).