git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Martin Langhoff (CatalystIT)" <martin@catalyst.net.nz>
To: Petr Baudis <pasky@suse.cz>
Cc: git@vger.kernel.org
Subject: Re: LCA2006 Git/Cogito tutorial
Date: Fri, 21 Oct 2005 16:02:28 +1300	[thread overview]
Message-ID: <43585A44.3050205@catalyst.net.nz> (raw)
In-Reply-To: <20051021005145.GB30889@pasky.or.cz>

Petr Baudis wrote:

> Dear diary, on Mon, Oct 17, 2005 at 02:48:09AM CEST, I got a letter
> where "Martin Langhoff (CatalystIT)" <martin@catalyst.net.nz> told me that...
> 
>>Petr Baudis hinted earlier that he might be coming, as did Linus (but
>>he was hoping for a sponsor, I'm not sure whether he'll be there or
>>not). Speak up if you'll be there!
> 
> 
> I'm sorry but I will not be there - it is too far away from my little
> country. :-(

Sad to hear that. I'll be soon in Europe, though, but not in CZ, 
unfortunately!

> (i) You might want to say "cg-export" instead of "git-tar-tree" (*shrug*)

You're right! I hadn't seen that.

> (ii) You say:
> 
> 	- Very fast stupid merge
> 	    ... and very smart, slow merges when stupid won't do
> 
>   What are you explicitly referring to? I don't think any kind of merge
> in GIT (unless something totally missed me) can be called "very smart".
> If it's a three-way merge, it's never "very smart".

See latest developments on git-merge.sh -- we should really revamp 
cg-merge ;)

> 	vim .gitignore

Then it'd be a bug, not a feature ;)

>>ps: lately, about 30% of my emails to git@vger from gmail have been 
>>dropped on the floor. This is starting to get annoying, is anyone seeing 
>>similar issues?
> 
> 
> Not me. Perhaps I'm in some VIP class. :^)

Oh, I figured that out! Gmail's "utf-8" mode encodes everything in 
base64. Awful sh*t. Reverted to ascii and life is good.



martin
-- 
-----------------------------------------------------------------------
Martin @ Catalyst .Net .NZ  Ltd, PO Box 11-053, Manners St,  Wellington
WEB: http://catalyst.net.nz/           PHYS: Level 2, 150-154 Willis St
OFFICE: +64(4)916-7224                              MOB: +64(21)364-017
       Make things as simple as possible, but no simpler - Einstein
-----------------------------------------------------------------------

      parent reply	other threads:[~2005-10-21  3:02 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-17  0:48 LCA2006 Git/Cogito tutorial Martin Langhoff (CatalystIT)
2005-10-21  0:51 ` Petr Baudis
2005-10-21  2:37   ` Dmitry Torokhov
2005-10-21  2:59     ` Martin Langhoff (CatalystIT)
2005-10-21  9:15       ` Petr Baudis
2005-10-23 15:35         ` Horst von Brand
2005-10-23 22:39           ` Petr Baudis
2005-10-24  8:32         ` Fredrik Kuivinen
2005-10-23 15:33       ` Horst von Brand
2005-10-23 22:40         ` Petr Baudis
2005-10-24  0:22           ` Horst von Brand
2005-10-24  6:25           ` Martin Langhoff
2005-10-24  0:58       ` Junio C Hamano
2005-10-24  1:35         ` Linus Torvalds
2005-10-24  1:48           ` Junio C Hamano
2005-10-24  3:32             ` Linus Torvalds
2005-10-24  7:54           ` Petr Baudis
2005-10-24  9:44             ` Junio C Hamano
2005-10-24 15:04             ` Linus Torvalds
2005-10-21  3:02   ` Martin Langhoff (CatalystIT) [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=43585A44.3050205@catalyst.net.nz \
    --to=martin@catalyst.net.nz \
    --cc=git@vger.kernel.org \
    --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).