From: James Purser <purserj@ksit.dynalias.com>
To: Petr Baudis <pasky@ucw.cz>
Cc: git@vger.kernel.org
Subject: Re: Cogito Tutorial If It Helps
Date: Wed, 27 Apr 2005 07:36:43 +1000 [thread overview]
Message-ID: <1114551403.3083.3.camel@kryten> (raw)
In-Reply-To: <20050426211834.GO13224@pasky.ji.cz>
On Wed, 2005-04-27 at 07:18, Petr Baudis wrote:
> Dear diary, on Tue, Apr 26, 2005 at 10:52:27PM CEST, I got a letter
> where James Purser <purserj@ksit.dynalias.com> told me that...
> > I reworked the previous tutorial to take in the changes in the scripts.
> > Will make this a series of tutorials to cover all aspects. Any
> > suggestions or hints or spelling corrections would be most welcome.
> >
> > http://ksit.dynalias.com/articles.php?s_id=46&art_id=41
>
> Thanks for writing that! :-)
>
> I'd vote for describing the cg-update right near cg-pull, or perhaps
> even before cg-update, as the primary method; I think it's commonly what
> people really want to do when they do cg-pull anyway.
>
> cg-merge is _not_ like doing cg-diff | cg-patch - that's a dangerous
> thought, and not true at all. cg-diff | cg-patch will just apply the
> given diff to your working directory, but it won't record any merging
> metadata, will often get it very wrong, and you will get to all sorts of
> other troubles. Just always use cg-merge. And probably pass it -b only
> when you know what are you doing.
>
> Thanks,
Thanks for that, I've changed it a little to point out that cg-patch
should really only be used for small single file patches.
--
James Purser
http://ksit.dynalias.com
next prev parent reply other threads:[~2005-04-26 21:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-26 20:52 Cogito Tutorial If It Helps James Purser
2005-04-26 21:18 ` Petr Baudis
2005-04-26 21:36 ` James Purser [this message]
2005-04-26 21:40 ` Petr Baudis
2005-04-27 18:22 ` Alan Chandler
2005-04-27 19:32 ` Petr Baudis
2005-04-27 22:15 ` Alan Chandler
2005-04-28 5:40 ` Alan Chandler
2005-04-28 0:48 ` Benjamin Herrenschmidt
2005-04-28 0:51 ` Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2005-04-27 0:45 James Purser
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=1114551403.3083.3.camel@kryten \
--to=purserj@ksit.dynalias.com \
--cc=git@vger.kernel.org \
--cc=pasky@ucw.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 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.