git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Marc-André Lureau" <marcandre.lureau@gmail.com>
To: "Felipe Contreras" <felipe.contreras@gmail.com>, git@vger.kernel.org
Cc: "Tor Arvid Lund" <torarvid@gmail.com>,
	"Christian Jaeger" <christian@jaeger.mine.nu>
Subject: Re: [ANNOUNCE] Git User's Survey 2008
Date: Fri, 5 Sep 2008 16:46:02 +0300	[thread overview]
Message-ID: <e29894ca0809050646g2f198890le2312d065696d1dd@mail.gmail.com> (raw)
In-Reply-To: <94a0d4530809030949v7c8c6ec4uc60bc873a40637d0@mail.gmail.com>

Hi

On Wed, Sep 3, 2008 at 7:49 PM, Felipe Contreras
<felipe.contreras@gmail.com> wrote:
> On Wed, Sep 3, 2008 at 3:46 PM, Tor Arvid Lund <torarvid@gmail.com> wrote:
>> On Wed, Sep 3, 2008 at 2:20 PM, Christian Jaeger
>> <christian@jaeger.mine.nu> wrote:
>>> I've found the many questions interesting as it showed me quite a number of
>>> interesting commands I didn't know about yet (so I said "never" to all of
>>> them, but that doesn't mean they aren't useful to me, just that I didn't
>>> know about them!):
>>
>> I agree 100% :-)
>
> Me too.

+Same for me. I am looking around for more information about some
commands/usage, but this is not always friendly with the man pages.

May I suggest to add a question next year: which email client do you
use to handle git attachements (if you do) ?

I cannot find yet a good workflow with either mutt, gmail or evolution
over imap.

If somebody could explain how they handle the git send-mail patches
they recieve, I would be thankful. How do you create .mbox files? What
is your workflow when you deal with mails?

Thank you for this great survey, 2008 edition !

-- 
Marc-André Lureau

  reply	other threads:[~2008-09-05 13:47 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-31 21:29 [ANNOUNCE] Git User's Survey 2008 Jakub Narebski
2008-09-01  5:13 ` Scott Chacon
2008-09-01  7:10   ` Felipe Contreras
2008-09-01  7:18 ` David John
2008-09-01  8:34   ` Jakub Narebski
2008-09-01  9:59     ` Karl Hasselström
2008-09-03 12:20     ` Christian Jaeger
2008-09-03 12:40       ` Eric Bowman
2008-09-03 12:46       ` Tor Arvid Lund
2008-09-03 16:49         ` Felipe Contreras
2008-09-05 13:46           ` Marc-André Lureau [this message]
2008-09-05 14:10             ` What do you use to send git patches? (was: [ANNOUNCE] Git User's Survey 2008) Jakub Narebski
2008-09-05 14:12             ` [ANNOUNCE] Git User's Survey 2008 Petr Baudis
2008-09-05 14:45             ` Jeff King
     [not found] ` <200809011305.35858.jnareb@gmail.com>
     [not found]   ` <20080901143718.GG10360@machine.or.cz>
2008-09-01 14:48     ` [ANNOUNCE] Git User's Survey 2008 has started Jakub Narebski
2008-09-01 14:51       ` Petr Baudis
2008-09-03 22:47 ` [ANNOUNCE] Git User's Survey 2008 Felipe Carvalho Oliveira
2008-09-06  9:11 ` Jakub Narebski
2008-09-08 22:58 ` Announcing " Jakub Narebski
2008-10-14  0:25 ` [ANNOUNCE] Git User's Survey 2008 has closed Jakub Narebski

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=e29894ca0809050646g2f198890le2312d065696d1dd@mail.gmail.com \
    --to=marcandre.lureau@gmail.com \
    --cc=christian@jaeger.mine.nu \
    --cc=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=torarvid@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).