From: Howard Miller <howard@e-learndesign.co.uk>
To: Martin Langhoff <martin.langhoff@gmail.com>
Cc: "Björn Steinbrink" <B.Steinbrink@gmx.de>, git@vger.kernel.org
Subject: Re: Commited to wrong branch
Date: Tue, 15 Sep 2009 15:11:57 +0100 [thread overview]
Message-ID: <26ae428a0909150711h1f7bc593j541d5eb7201a7e45@mail.gmail.com> (raw)
In-Reply-To: <46a038f90909150654t73cab47ckfd02f8a2f4353722@mail.gmail.com>
2009/9/15 Martin Langhoff <martin.langhoff@gmail.com>:
> 2009/9/15 Björn Steinbrink <B.Steinbrink@gmx.de>:
>> [Please stop top-posting...]
>
> Not everyone is deep in mailing-list lore :-) -- we can help anyway.
>
> Howard, I see you're wondering about it: http://www.idallen.com/topposting.html
>
>> Just don't use patch(1), there's no sane reason to do that, you're
>> sacrificing all of what git can offer there.
>
> Oh, yes there is, specially for newcomers used to patch, and how it
> handles conflicts.
>
> In this case, I happen to know that Howard is a refugee from CVS land
> (the moodle project in this case), and he is familiar with the output
> of patch if things go wrong.
>
> It's not what I'd recommend to someone that is deep in git-land. But
> even myself (with a bit of code in git) sometimes use patch when
> git-apply tries to be too clever and I just want a damn .rej file to
> review and edit with emacs.
>
> cheers,
>
>
> m
> --
> martin.langhoff@gmail.com
> martin@laptop.org -- School Server Architect
> - ask interesting questions
> - don't get distracted with shiny stuff - working code first
> - http://wiki.laptop.org/go/User:Martinlanghoff
>
...and I still don't understand cvs either :-)
(NB. I have put my reply at the bottom where nobody will see it - this
is why forums are better than mailing lists.... >ducks<)
next prev parent reply other threads:[~2009-09-15 14:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-15 10:31 Commited to wrong branch Howard Miller
2009-09-15 10:55 ` Martin Langhoff
2009-09-15 11:05 ` Howard Miller
2009-09-15 11:16 ` Martin Langhoff
2009-09-15 12:10 ` Howard Miller
2009-09-15 12:46 ` Martin Langhoff
2009-09-15 12:58 ` Howard Miller
2009-09-15 13:06 ` Björn Steinbrink
2009-09-15 13:12 ` Howard Miller
2009-09-15 13:54 ` Martin Langhoff
2009-09-15 14:11 ` Howard Miller [this message]
2009-09-15 20:39 ` Björn Steinbrink
2009-09-15 20:52 ` Howard Miller
2009-09-15 21:53 ` Martin Langhoff
2009-09-15 22:30 ` Björn Steinbrink
2009-09-15 13:27 ` Howard Miller
2009-09-15 13:45 ` Howard Miller
2009-09-15 14:08 ` Johannes Sixt
2009-09-15 13:46 ` Martin Langhoff
2009-09-15 11:19 ` Björn Steinbrink
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=26ae428a0909150711h1f7bc593j541d5eb7201a7e45@mail.gmail.com \
--to=howard@e-learndesign.co.uk \
--cc=B.Steinbrink@gmx.de \
--cc=git@vger.kernel.org \
--cc=martin.langhoff@gmail.com \
/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).