From: Eric Raible <raible@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org, david.hagood@gmail.com
Subject: Re: Problems with GIT under Windows - "not uptodate"
Date: Tue, 1 Sep 2009 16:16:21 -0700 [thread overview]
Message-ID: <279b37b20909011616x60fc7bfav22daca1bc7bfc714@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0909020052550.8306@pacific.mpi-cbg.de>
On Tue, Sep 1, 2009 at 3:56 PM, Johannes
Schindelin<Johannes.Schindelin@gmx.de> wrote:
> Hi,
>
> Eric, is there any good reason you neglect netiquette? I re-added David
> to the Cc: list.
Thanks. Frankly I (stupidly) assumed that gmane.org would handle it.
Educate me (if you would): if I read the git list via gmane, what's the
best way to follow up?
next prev parent reply other threads:[~2009-09-01 23:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-01 15:46 Problems with GIT under Windows - "not uptodate" david.hagood
2009-09-01 16:52 ` Eric Raible
2009-09-01 22:56 ` Johannes Schindelin
2009-09-01 23:16 ` Eric Raible [this message]
2009-09-01 23:19 ` Johannes Schindelin
2009-09-01 18:19 ` skillzero
2009-09-01 18:25 ` david.hagood
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=279b37b20909011616x60fc7bfav22daca1bc7bfc714@mail.gmail.com \
--to=raible@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=david.hagood@gmail.com \
--cc=git@vger.kernel.org \
/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).